Okay this is a weird forum interface - I go here and it tells me this is the bug tracker and go to /support - I go there and it says if I want to discuss in the community come back here. I’m confused so I’m going to post anyway, sorry if this is in the wrong place.
I’ve installed ownCloud server using docker-compose from the official docker-compose.yml. It’s set to restart automatically at boot.
For whatever reason when I reboot the server the owncloud/server:10.0.10 container fails:
48ae8b018790 owncloud/server:10.0.10 “/usr/bin/entrypoint…” 13 hours ago Exited (137) 3 minutes ago 0.0.0.0:85->8080/tcp app_owncloud_1
The containers for mariadb and redis continue humming along. I then have to go into the directory where the yml file is and do “docker-compose down” followed by “docker-compose up -d” and then everything is fine.
Any ideas what I’m doing wrong here? It should be pretty cut and dry and my google-fu is failing me, I can’t find anyone else reporting this problem.
NOTE: I just realized 10.2.0 is out (I had a hard time finding what the latest version was when I first installed) so I just changed to it. We’ll see if that helps.
NOTE2: Under 10.2.0 it still does the same thing:
:~$ docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
04bc71c47149 owncloud/server:10.2.0 “/usr/bin/entrypoint…” 9 minutes ago Exited (137) 4 minutes ago 0.0.0.0:85->8080/tcp app_owncloud_1
ca265b1bb90d webhippie/mariadb:latest “/usr/bin/entrypoint…” 9 minutes ago Up 3 minutes (healthy) 3306/tcp app_db_1
6b076915ae4a webhippie/redis:latest “/usr/bin/entrypoint…” 9 minutes ago Up 3 minutes (healthy) 6379/tcp app_redis_1
Ok, so the logs look like the owncloud container even started serving requests, but then just went away?
This tells me it was probably killed from outside. How much memory do you have? Is there an OOM killer running? Check your docker0 (the system where your containers are running on) system logs, it should show if something was killed.
I quick search for your error ‘docker container exited 137’ confirms my theory.
The system has 16 GB of RAM and with everything running only 5 GB is in use.
This only occurs at system startup and only affects the Apache container of ownCloud. The others keep running. Once i shut down and restart the containers with docker-compose they stay up fine until next reboot.
I’m not sure how to check the docker0 system logs…? Do you mean the logs in /var/log/kern.log?
Depends on your system, on a systemd linux system you should be able to analyze your logs with the journalctl command. Just search for ‘oom’ or ‘out of memory’.
Perhaps there are memory limits configured for the single containers, not sure how this exactly works, but that’s where I would look first.