Closed apiontek closed 2 years ago
Just to add, if I attach to the container and perform:
rm /usr/bin/websocat && \
wget -c https://github.com/vi/websocat/releases/download/v1.9.0/websocat_linux64 -O /usr/bin/websocat && \
chmod +x /usr/bin/websocat
And then restart the container, autostart of calibre & content server works as expected, without the need to access the guacamole endpoint first.
We already fixed it in the baseimage a couple of days ago. It should have propagated to the latest calibre version build pushed earlier today.
Yes, this is working now.
Expected Behavior
I want to run calibre with the content server automatically starting. Once configured and working, if I restart the container, or stop and start it, I would expect calibre and its content server to automatically start, and the content server to be accessible at my endpoint, without me needing to connect to the separate guacamole endpoint.
Current Behavior
Currently, once I connect to the guacamole endpoint, then calibre starts and the content server becomes accessible.
However, if I launch the container and do not connect to the guacamole endpoint, calibre does not start inside the container and the content server remains dead.
I'm seeing an error during container launch:
And when I attach to the container (
docker exec -i -t xxxxxx /bin/bash
) and docat /usr/bin/websocat
it's just a text file saying "Not Found"Steps to Reproduce
Environment
OS: Ubuntu 20.04.3 LTS CPU architecture: x86_64 How docker service was installed: official docker repo
Command used to create docker container (run/create/compose/screenshot)
compose yaml:
.env file:
Docker logs