Shinyproxy Docker with keycloak: failed to start

[dmenne]

Which showed to be a simple permission error for docker.sock

Not so simple, though:

Docker-compose vs. running docker from cmd: .sock-problem

When I run my shinyproxy container with the method described here, everything works fine. Trying to do the same with docker-compose (or, same effect, docker compose swarm) fails with authorization error on docker.sock. The file is set chown root:docker on each docker startup; when I set this to chown dieter:docker, where dieter is the user, all is well, but I have to do this after each docker startup. I am sure that dieter is in group docker - confirmed by the working command line version. I …