Defect #40360
closed
Can't migrate dockerized Redmine instance
0%
Description
1. Set up docker compose redmine instance using public docker hub image so that mysql /var/lib/mysql has it's own volume for backup purposes.
2. Create new docker compose redmine instance and mount the MySQL volume to /var/live/mysql of that new instance's MySQL sidecar container.
Redmine will get confused and try to run migrations. Docker Hub page contains no information on which paths need to be backed up and moved over to new instances if migration is required.
Updated by tomy shen about 2 months ago
Basically there will be the following three directories that need to be backed up:
- redmine/files:/usr/src/redmine/files
- redmine/plugins:/usr/src/redmine/plugins
- redmine/themes:/usr/src/redmine/public/themes
Updated by Holger Just about 2 months ago
- Status changed from New to Closed
- Resolution set to Invalid
Unfortunately, the Redmine project does not maintain any docker images. The so called Official Image is maintained as a separate project by a separate set of people. Please check the image page and their source repository for support options.
For general hints about backing up Redmine, please see RedmineBackupRestore.
In any case, please use the issue tracker for bug reports or feature requests only. Usage and admin questions should be asked in the forums preferably.