docker-compose is not starting

[danieldeusing]

Yesterday I installed owncloud with docker-compose and everything worked fine.

This night the server got kernel panic, I dont know why. This never happened before. Anyways ... I cannot start owncloud. It is saying this and then restarting:

docker-compose up -d

db_1        | Cron is enabled, launching it!
redis_1     | 12:C 30 Apr 08:42:44.142 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
db_1        | 180430 08:42:44 mysqld_safe Logging to '/var/lib/mysql/ea22b4ff443b.err'.
redis_1     | 12:C 30 Apr 08:42:44.142 # Redis version=4.0.9, bits=64, commit=757d0c15, modified=0, pid=12, just started
owncloud_1  | Creating volume folders...
redis_1     | 12:C 30 Apr 08:42:44.142 # Configuration loaded
owncloud_1  | Creating hook folders...
redis_1     | 12:M 30 Apr 08:42:44.145 * Running mode=standalone, port=6379.
db_1        | 180430 08:42:44 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
owncloud_1  | Waiting for MySQL...
redis_1     | 12:M 30 Apr 08:42:44.146 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
redis_1     | 12:M 30 Apr 08:42:44.146 # Server initialized
redis_1     | 12:M 30 Apr 08:42:44.146 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
redis_1     | 12:M 30 Apr 08:42:44.146 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command 'echo never > /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after THP is disabled.
redis_1     | 12:M 30 Apr 08:42:44.146 * Ready to accept connections
owncloud_1  | wait-for-it: waiting 180 seconds for db:3306
owncloud_1  | wait-for-it: db:3306 is available after 0 seconds
owncloud_1  | Removing custom folder...
owncloud_1  | Linking custom folder...
owncloud_1  | Removing config folder...
owncloud_1  | Linking config folder...
owncloud_1  | Copying db file...
owncloud_1  | Copying utf8mb4 config...
owncloud_1  | Fixing hook perms...
owncloud_1  | Fixing base perms...
owncloud_1  | Fixing data perms...
owncloud_1  | Upgrading server database...
owncloud_1  | ownCloud is already latest version
ownclouddockerserver_owncloud_1 exited with code 3

[madchap]

I have the same behavior without docker-compose.

Since the last automated "watchtower" update (April 27th), my owncloud container refuses to start.
This is using the container image with this hash:

sha256:1aba0871ce6a82d84850427001cc9f7cbd10b17815b04181414bfa5c3290f648

[tboerger]

Investigating it, stay tuned.

[tboerger]

Please upgrade the docker image with docker-compose pull, the issue have been resolved.