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
Perhaps there isn't too much that you can do about this, but running the server normally with sudo shows docker support "Docker is installed and running (Client version: 17.12.1-ce, Client API Version: 1.35)" while running the daemon version shows it as disabled. I suspect this is because the daemon reduces itself to a regular user after port binding so it no longer has the credentials to start docker containers. This could be overcome by allowing normal users to run docker containers, but that is perhaps worse from a security standpoint than leaving the daemon with sudo. Maybe the daemon version could present a more specific error message, I noticed this quickly, but I can imagine someone trying to get it to pick up on their docker and not realizing it was a permissions issue.
The text was updated successfully, but these errors were encountered:
Perhaps there isn't too much that you can do about this, but running the server normally with sudo shows docker support "Docker is installed and running (Client version: 17.12.1-ce, Client API Version: 1.35)" while running the daemon version shows it as disabled. I suspect this is because the daemon reduces itself to a regular user after port binding so it no longer has the credentials to start docker containers. This could be overcome by allowing normal users to run docker containers, but that is perhaps worse from a security standpoint than leaving the daemon with sudo. Maybe the daemon version could present a more specific error message, I noticed this quickly, but I can imagine someone trying to get it to pick up on their docker and not realizing it was a permissions issue.
The text was updated successfully, but these errors were encountered: