Troubleshooting
Permission denied on the Docker socket
Section titled “Permission denied on the Docker socket”dial unix /var/run/docker.sock: connect: permission deniedThis error means the user running Hoister is not a member of the docker group. Add the user (replace foo with the actual username) and then re-login or start a new shell session:
sudo usermod -aG docker fooIf you are running Hoister as a container and still see this error, make sure the socket is mounted correctly:
volumes: - /var/run/docker.sock:/var/run/docker.sockContainer does not get updated
Section titled “Container does not get updated”- Confirm the label
hoister.enable=trueis set on the target service. - Check that Hoister has access to the registry. For private registries see the Registries guide.
- Increase log verbosity by setting
RUST_LOG=debugon the Hoister container to see what is happening.
Rollback was triggered unexpectedly
Section titled “Rollback was triggered unexpectedly”Hoister marks an update as failed when the container exits with a non-zero code or does not become healthy within the configured timeout. Check the container logs of the updated service to find the root cause:
docker logs <container-name>