Closed lingfengchencn closed 7 years ago
@lingfengchencn we need to know the image version u are using
docker images | grep redmine
[root@... redmine]# docker images | grep redmine
sameersbn/redmine 3.4.2 1808ef524744 2 months ago 670MB
and now I get a new error when I rerun the command.
[root@... redmine]# docker-compose up redmine
redmine_mysql_1 is up-to-date
Recreating redmine_redmine_1 ...
Recreating redmine_redmine_1 ... done
Attaching to redmine_redmine_1
redmine_1 | Initializing logdir...
redmine_1 | Initializing datadir...
redmine_1 | Symlinking dotfiles...
redmine_1 | Installing configuration templates...
redmine_1 | Configuring redmine...
redmine_1 | Configuring redmine::database
redmine_1 | Configuring redmine::unicorn...
redmine_1 | Configuring redmine::secret_token...
redmine_1 | Generating a session token...
redmine_1 | Note:
redmine_1 | All old sessions will become invalid.
redmine_1 | Please specify the REDMINE_SECRET_TOKEN parameter for persistence.
redmine_1 | **SHOULD** be defined if you have a load-balancing Redmine cluster.
redmine_1 | Configuring redmine::max_concurrent_ajax_uploads...
redmine_1 | Configuring redmine::sudo_mode...
redmine_1 | Configuring redmine::autologin_cookie...
redmine_1 | Configuring redmine::backups...
redmine_1 | Configuring nginx...
redmine_1 | Configuring nginx::redmine...
redmine_1 | Migrating database. Please be patient, this could take a while...
redmine_1 | redmine_production already exists
redmine_1 | rm: cannot remove '/home/redmine/redmine/vendor/bundle/ruby/2.3.0/bin': Directory not empty
redmine_1 | rm: cannot remove '/home/redmine/redmine/vendor/bundle/ruby/2.3.0/cache': Directory not empty
redmine_1 | rm: cannot remove '/home/redmine/redmine/vendor/bundle/ruby/2.3.0/extensions/x86_64-linux/2.3.0/kgio-2.11.0': Directory not empty
...
redmine_1 | rm: cannot remove '/home/redmine/redmine/vendor/bundle/ruby/2.3.0/specifications': Directory not empty
redmine_redmine_1 exited with code 1
@lingfengchencn sorry i think there is something strange with your system docker does always the same for all people i can't reproduce so you probally installed something custom
simply delete your local volumes and start from scratch
Yes , I tried。 everything works fine on my mac, But can't work on my server。。
@lingfengchencn maybe you forgoten to tune selinux read about it in this readme because your centos user that could block filesystem
Note I am seeing the "Bundler::GemNotFound" in the sameersbn/redmine:3.4.2 image but only after I deleted the redmine data directory before starting image.
$ sudo rm -rf /srv/docker/redmine/
$ docker pull sameersbn/redmine:3.4.2
3.4.2: Pulling from sameersbn/redmine
Digest: sha256:be1233d7f48af8f13a72e897f5492414107402c948fe47f533820ca02b599b17
Status: Image is up to date for sameersbn/redmine:3.4.2
$ docker-compose up
Starting dockerredmine_postgresql_1
Starting dockerredmine_redmine_1
Attaching to dockerredmine_postgresql_1, dockerredmine_redmine_1
postgresql_1 | Initializing datadir...
postgresql_1 | Initializing certdir...
postgresql_1 | Initializing logdir...
postgresql_1 | Initializing rundir...
postgresql_1 | Setting resolv.conf ACLs...
postgresql_1 | Initializing database...
redmine_1 | Initializing logdir...
redmine_1 | Initializing datadir...
redmine_1 | Generating OpenSSH client keys...
redmine_1 | Symlinking dotfiles...
redmine_1 | Installing configuration templates...
redmine_1 | Configuring redmine...
postgresql_1 | Configuring hot standby...
postgresql_1 | ‣ Setting postgresql.conf parameter: wal_level = 'hot_standby'
postgresql_1 | ‣ Setting postgresql.conf parameter: max_wal_senders = '16'
postgresql_1 | ‣ Setting postgresql.conf parameter: checkpoint_segments = '8'
postgresql_1 | ‣ Setting postgresql.conf parameter: wal_keep_segments = '32'
postgresql_1 | ‣ Setting postgresql.conf parameter: hot_standby = 'on'
postgresql_1 | ‣ Setting postgresql.conf parameter: data_directory = '/var/lib/postgresql/9.6/main'
postgresql_1 | ‣ Setting postgresql.conf parameter: log_directory = '/var/log/postgresql'
postgresql_1 | ‣ Setting postgresql.conf parameter: log_filename = 'postgresql-9.6-main.log'
postgresql_1 | ‣ Setting postgresql.conf parameter: ssl = 'off'
postgresql_1 | Creating database user: redmine
postgresql_1 | Creating database: redmine_production...
postgresql_1 | ‣ Granting access to redmine user...
postgresql_1 | Starting PostgreSQL 9.6...
postgresql_1 | LOG: database system was shut down at 2017-09-26 14:07:10 UTC
postgresql_1 | LOG: MultiXact member wraparound protections are now enabled
postgresql_1 | LOG: database system is ready to accept connections
postgresql_1 | LOG: autovacuum launcher started
redmine_1 | Configuring redmine::database.....
redmine_1 | Configuring redmine::unicorn...
redmine_1 | Configuring redmine::secret_token...
redmine_1 | Generating a session token...
redmine_1 | Note:
redmine_1 | All old sessions will become invalid.
redmine_1 | Please specify the REDMINE_SECRET_TOKEN parameter for persistence.
redmine_1 | **SHOULD** be defined if you have a load-balancing Redmine cluster.
redmine_1 | Configuring redmine::max_concurrent_ajax_uploads...
redmine_1 | Configuring redmine::sudo_mode...
redmine_1 | Configuring redmine::autologin_cookie...
redmine_1 | Configuring redmine::backups...
redmine_1 | Configuring nginx...
redmine_1 | Configuring nginx::redmine...
redmine_1 | Migrating database. Please be patient, this could take a while...
redmine_1 | Bundler::GemNotFound: Could not find gem 'rails (= 4.2.8)' in any of the gem sources listed in your Gemfile.
redmine_1 | /var/lib/gems/2.3.0/gems/bundler-1.15.4/lib/bundler/resolver.rb:396:in `block in verify_gemfile_dependencies_are_found!'
redmine_1 | /var/lib/gems/2.3.0/gems/bundler-1.15.4/lib/bundler/resolver.rb:366:in `each'
redmine_1 | /var/lib/gems/2.3.0/gems/bundler-1.15.4/lib/bundler/resolver.rb:366:in `verify_gemfile_dependencies_are_found!'
redmine_1 | /var/lib/gems/2.3.0/gems/bundler-1.15.4/lib/bundler/resolver.rb:212:in `start'
redmine_1 | /var/lib/gems/2.3.0/gems/bundler-1.15.4/lib/bundler/resolver.rb:191:in `resolve'
redmine_1 | /var/lib/gems/2.3.0/gems/bundler-1.15.4/lib/bundler/definition.rb:235:in `resolve'
redmine_1 | /var/lib/gems/2.3.0/gems/bundler-1.15.4/lib/bundler/definition.rb:159:in `specs'
redmine_1 | /var/lib/gems/2.3.0/gems/bundler-1.15.4/lib/bundler/definition.rb:218:in `specs_for'
redmine_1 | /var/lib/gems/2.3.0/gems/bundler-1.15.4/lib/bundler/definition.rb:207:in `requested_specs'
redmine_1 | /var/lib/gems/2.3.0/gems/bundler-1.15.4/lib/bundler/runtime.rb:109:in `block in definition_method'
redmine_1 | /var/lib/gems/2.3.0/gems/bundler-1.15.4/lib/bundler/runtime.rb:21:in `setup'
redmine_1 | /var/lib/gems/2.3.0/gems/bundler-1.15.4/lib/bundler.rb:101:in `setup'
redmine_1 | /var/lib/gems/2.3.0/gems/bundler-1.15.4/lib/bundler/setup.rb:19:in `<top (required)>'
redmine_1 | /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
redmine_1 | /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
dockerredmine_redmine_1 exited with code 1
However this seems to be solved if I also make sure to delete the containers.
$ docker-compose rm
Going to remove dockerredmine_redmine_1, dockerredmine_postgresql_1
Are you sure? [yN] y
Removing dockerredmine_redmine_1 ... done
Removing dockerredmine_postgresql_1 ... done
$ sudo rm -rf /srv/docker/redmine/
$ docker-compose up
Creating dockerredmine_postgresql_1
Creating dockerredmine_redmine_1
Attaching to dockerredmine_postgresql_1, dockerredmine_redmine_1
postgresql_1 | Initializing datadir...
postgresql_1 | Initializing certdir...
redmine_1 | Initializing logdir...
postgresql_1 | Initializing logdir...
postgresql_1 | Initializing rundir...
postgresql_1 | Setting resolv.conf ACLs...
postgresql_1 | Initializing database...
redmine_1 | Initializing datadir...
redmine_1 | Generating OpenSSH client keys...
redmine_1 | Symlinking dotfiles...
redmine_1 | Installing configuration templates...
redmine_1 | Configuring redmine...
postgresql_1 | Configuring hot standby...
postgresql_1 | ‣ Setting postgresql.conf parameter: wal_level = 'hot_standby'
postgresql_1 | ‣ Setting postgresql.conf parameter: max_wal_senders = '16'
postgresql_1 | ‣ Setting postgresql.conf parameter: checkpoint_segments = '8'
postgresql_1 | ‣ Setting postgresql.conf parameter: wal_keep_segments = '32'
postgresql_1 | ‣ Setting postgresql.conf parameter: hot_standby = 'on'
postgresql_1 | ‣ Setting postgresql.conf parameter: data_directory = '/var/lib/postgresql/9.6/main'
postgresql_1 | ‣ Setting postgresql.conf parameter: log_directory = '/var/log/postgresql'
postgresql_1 | ‣ Setting postgresql.conf parameter: log_filename = 'postgresql-9.6-main.log'
postgresql_1 | ‣ Setting postgresql.conf parameter: ssl = 'off'
postgresql_1 | Creating database user: redmine
postgresql_1 | Creating database: redmine_production...
postgresql_1 | ‣ Granting access to redmine user...
postgresql_1 | Starting PostgreSQL 9.6...
postgresql_1 | LOG: database system was shut down at 2017-09-26 14:33:26 UTC
postgresql_1 | LOG: MultiXact member wraparound protections are now enabled
postgresql_1 | LOG: autovacuum launcher started
postgresql_1 | LOG: database system is ready to accept connections
redmine_1 | Configuring redmine::database.....
redmine_1 | Configuring redmine::unicorn...
redmine_1 | Configuring redmine::secret_token...
redmine_1 | Generating a session token...
redmine_1 | Note:
redmine_1 | All old sessions will become invalid.
redmine_1 | Please specify the REDMINE_SECRET_TOKEN parameter for persistence.
redmine_1 | **SHOULD** be defined if you have a load-balancing Redmine cluster.
redmine_1 | Configuring redmine::max_concurrent_ajax_uploads...
redmine_1 | Configuring redmine::sudo_mode...
redmine_1 | Configuring redmine::autologin_cookie...
redmine_1 | Configuring redmine::backups...
redmine_1 | Configuring nginx...
redmine_1 | Configuring nginx::redmine...
redmine_1 | Migrating database. Please be patient, this could take a while...
postgresql_1 | ERROR: database "redmine_production" already exists
postgresql_1 | STATEMENT: CREATE DATABASE "redmine_production" ENCODING = 'unicode'
redmine_1 | redmine_production already exists
redmine_1 | Installing plugins...
redmine_1 | Installing gems required by plugins...
redmine_1 | Migrating plugins. Please be patient, this could take a while...
redmine_1 | Installing themes...
redmine_1 | 2017-09-26 20:03:46,036 CRIT Supervisor running as root (no user in config file)
redmine_1 | 2017-09-26 20:03:46,036 WARN Included extra file "/etc/supervisor/conf.d/cron.conf" during parsing
redmine_1 | 2017-09-26 20:03:46,036 WARN Included extra file "/etc/supervisor/conf.d/nginx.conf" during parsing
redmine_1 | 2017-09-26 20:03:46,036 WARN Included extra file "/etc/supervisor/conf.d/unicorn.conf" during parsing
redmine_1 | 2017-09-26 20:03:46,057 INFO RPC interface 'supervisor' initialized
redmine_1 | 2017-09-26 20:03:46,057 CRIT Server 'unix_http_server' running without any HTTP authentication checking
redmine_1 | 2017-09-26 20:03:46,057 INFO supervisord started with pid 1
redmine_1 | 2017-09-26 20:03:47,060 INFO spawned: 'unicorn' with pid 408
redmine_1 | 2017-09-26 20:03:47,060 INFO spawned: 'cron' with pid 409
redmine_1 | 2017-09-26 20:03:47,062 INFO spawned: 'nginx' with pid 410
redmine_1 | 2017-09-26 20:03:48,403 INFO success: unicorn entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
redmine_1 | 2017-09-26 20:03:48,403 INFO success: cron entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
redmine_1 | 2017-09-26 20:03:48,403 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
Yes,
I run docker-compose up redmine
at the first time, I got GemNotFound
exception;
but the second time, I got Directory not empty
,and then I followed these commands:
docker-compose rm
docker-compose rmi
docker-composer up -d mysql redmine
...
docker-composer logs -f redmine
redmine_1 | redmine_production already exists
redmine_1 | rm: cannot remove '/home/redmine/redmine/vendor/bundle/ruby/2.3.0/bin': Directory not empty
Did you check to see if you have selinux enabled and whether disabling it helps?
On Tue, Sep 26, 2017 at 11:13 AM, LingFeng.Chen.Cn <notifications@github.com
wrote:
Yes, I run docker-compose up redmine at the first time, I got GemNotFound exception;
but the second time, I got Directory not empty,and then I followed these commands:
docker-compose rm docker-compose rmi docker-composer up -d mysql redmine
...
docker-composer logs -f redmine
redmine_1 | redmine_production already exists redmine_1 | rm: cannot remove '/home/redmine/redmine/vendor/bundle/ruby/2.3.0/bin': Directory not empty
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/sameersbn/docker-redmine/issues/311#issuecomment-332231290, or mute the thread https://github.com/notifications/unsubscribe-auth/AFWomSbBsnM1aCTMKx2PHth__QLYerKEks5smRR0gaJpZM4PiGMJ .
-- Jonathan Cormier Software Engineer
Voice: 315.425.4045 <%28315%29%20425-4045> x222
[image: Inline image 1] http://www.CriticalLink.com http://www.criticallink.com/ 6712 Brooklawn Parkway, Syracuse, NY 13211
https://www.linkedin.com/company/critical-link-llc https://twitter.com/Critical_Link
Its 100% selinux i am pritty sure as i wrote befor
most centos users don't understand that they are running enterprise red hat driven distribution :) as cloud provider let them simply install the image and then they are left alone
Yes, i set SELinux enabled.
but still directory not empty
.
docker rm \ rmi docker up redmine
...director not empty...
set selinux to enable , can fix gem not found . tks @frank-dspeed
directory not empty
see #260
when I up redmine, I got the following error info.
env