You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While testing to update images for traefik (3.3.3 --> 3.3.4, ok) and collabora, collabora fails to start. Tested on my Hetzner deployment.
Updating the collabora image from 24.04.12.3.1 to 24.04.12.4.1, a patch release which was published some days ago, the container does not start anymore and responds with the following cryptic error message. When switching back to 24.04.12.3.1, all works fine:
docker images
traefik v3.3.4 e49b83f3e049 22 hours ago 190MB
collabora/code 24.04.12.4.1 d3bfb5a571cb 5 days ago 1.43GB
collabora/code 24.04.12.3.1 e9fb61f587aa 2 weeks ago 1.43GB
onlyoffice/documentserver 8.3.0 497c96127bfc 2 weeks ago 3.54GB
traefik v3.3.3 1c768f87626a 3 weeks ago 190MB
owncloud/ocis latest ccb91a2b7514 2 months ago 186MB
owncloud/ocis-rolling 7.0.0 e0688db571c1 2 months ago 186MB
owncloud/ocis-rolling latest 00564f82b13f 4 months ago 185MB
apache/tika latest-full 6c5f30726faa 4 months ago 733MB
docker compose ps -a --format "table {{.Service}}\t{{.State}}\t{{.ID}}"
SERVICE STATE CONTAINER ID
collabora restarting eefedafbef2d
collaboration created e36b13edb49d
collaboration-oo running 4aab9af30c59
ocis running a68251298c39
onlyoffice running 1d5131f9d6c1
tika running bb3bd87c8190
traefik running 8e8fcd95cb24
docker logs eefedafbef2d 2>&1 | less
Unknown option specified: c
Note that we have for a good reason a defined image for traefik, collabora and onlyoffice to avoid such scenarios in production, the currently used images as shown above deploy well.
Creating containers with working/not working images, the following shows up.
Running the command coolconfig generate-proof-key in the containers shell produces different results:
With working images, the command succeeds. The container is still up and running after the command.
With non working images, the command fails. The container closes like when you shut it down.
The bad thing is, that you cant see if there is an error because the container just crashed, there is no output
While testing to update images for traefik (3.3.3 --> 3.3.4, ok) and collabora, collabora fails to start. Tested on my Hetzner deployment.
Updating the collabora image from
24.04.12.3.1
to24.04.12.4.1
, a patch release which was published some days ago, the container does not start anymore and responds with the following cryptic error message. When switching back to24.04.12.3.1
, all works fine:Note that we have for a good reason a defined image for traefik, collabora and onlyoffice to avoid such scenarios in production, the currently used images as shown above deploy well.
@kobergj @2403905 we need to investigate after 7.1
The text was updated successfully, but these errors were encountered: