Content
Docker fails starting web-service
Added by Michael Albert almost 9 years ago
Hi,
I tried to run the docker container with the description here: [[https://www.openproject.org/open-source/download/docker/]]
Even if I use the very simple configuration (first docker run command) the web service keeps cycling at startup..
@
…
——-> Database setup finished.
On first installation, the default admin credentials are login: admin, password: admin
——-> Launching supervisord…
/usr/lib/python2.7/dist-packages/supervisor/options.py:296: UserWarning: Supervisord is running as root and it is searching for its configuration file in default locations (including its current working directory); you probably want to specify a “-c” argument specifying an absolute path to a configuration file for improved security.
‘Supervisord is running as root and it is searching ’
2016-04-22 09:01:40,353 CRIT Supervisor running as root (no user in config file)
2016-04-22 09:01:40,353 WARN Included extra file “/etc/supervisor/conf.d/supervisord.conf” during parsing
2016-04-22 09:01:41,913 INFO RPC interface ‘supervisor’ initialized
2016-04-22 09:01:41,914 CRIT Server ‘unix_http_server’ running without any HTTP authentication checking
2016-04-22 09:01:41,918 INFO supervisord started with pid 1
2016-04-22 09:01:42,932 INFO spawned: ‘postgres’ with pid 152
2016-04-22 09:01:42,956 INFO spawned: ‘apache2’ with pid 153
2016-04-22 09:01:42,968 INFO spawned: ‘web’ with pid 154
2016-04-22 09:01:42,986 INFO spawned: ‘worker’ with pid 155
2016-04-22 09:01:43,024 INFO spawned: ‘postfix’ with pid 157
2016-04-22 09:01:43,040 INFO spawned: ‘memcached’ with pid 158
2016-04-22 09:01:43,130 INFO success: postfix entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2016-04-22 09:01:43,935 INFO success: postgres entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2016-04-22 09:01:43,935 INFO success: apache2 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2016-04-22 09:01:44,747 INFO success: web entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2016-04-22 09:01:44,748 INFO success: worker entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2016-04-22 09:01:44,750 INFO success: memcached entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2016-04-22 09:01:44,752 INFO exited: postfix (exit status 0; expected)
2016-04-22 09:01:51,351 INFO exited: web (exit status 1; not expected)
2016-04-22 09:01:52,359 INFO spawned: ‘web’ with pid 339
2016-04-22 09:01:53,361 INFO success: web entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2016-04-22 09:01:55,677 INFO exited: web (exit status 1; not expected)
2016-04-22 09:01:56,685 INFO spawned: ‘web’ with pid 345
2016-04-22 09:01:57,688 INFO success: web entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2016-04-22 09:01:59,941 INFO exited: web (exit status 1; not expected)
2016-04-22 09:02:00,952 INFO spawned: ‘web’ with pid 351
2016-04-22 09:02:01,954 INFO success: web entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2016-04-22 09:02:04,112 INFO exited: web (exit status 1; not expected)
2016-04-22 09:02:05,122 INFO spawned: ‘web’ with pid 361
2016-04-22 09:02:06,125 INFO success: web entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2016-04-22 09:02:08,062 INFO exited: web (exit status 1; not expected)
2016-04-22 09:02:09,071 INFO spawned: ‘web’ with pid 368
2016-04-22 09:02:10,073 INFO success: web entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2016-04-22 09:02:12,510 INFO exited: web (exit status 1; not expected)
…
@
Any ideas to solve that?
Replies (3)
I just checked with the latest version of the docker image, and it starts fine on my machine. Could you send the result of running
docker exec -it CONTAINER_ID bash -c "cat /var/log/supervisor/*.log".CONTAINER_IDcan be obtained using thedocker pscommand.eWe set up a different machine with an other host OS (now Debian instead of Ubuntu) and everything works fine from the beginning. I have no idea what went wrong on the other machine and I doubt that we will investigate that further. Thanks for your help!
Michael, are you getting the following? That was my case with 512 MB …
grep memory /var/lib/openproject/logs/web-stderr.log
/usr/local/bundle/gems/passenger-5.0.22/src/ruby_supportlib/phusion_passenger/platform_info/operating_system.rb:123:in ``’: Cannot allocate memory - /bin/uname (Errno::ENOMEM)
I had run the following commands:
sudo mkdir -p /var/lib/openproject/{pgdata,logs,static}
docker run -d -p 80:80 —name openproject -e SECRET_KEY_BASE=secret \
-v /var/lib/openproject/pgdata:/var/lib/postgresql/9.4/main \
-v /var/lib/openproject/logs:/var/log/supervisor \
-v /var/lib/openproject/static:/var/db/openproject \
openproject/community:5.0