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
I'd like to suggest that the default docker user id being assigned as 'nobody' be mentioned somewhere in the docker installation documentation.
This is breaking for some installation configurations (mine: small experimental lab with Portainer as root, which results in a container that looks running but isn't actually working...my level of frustration at struggling fo 2 hours to figure out why a container wont deploy, only to find an issue 7 years old, but undocumented without digging into git to find it.....)
I don't have the requisite experience or time to make a pull request on this.
My thought would be to use language like this: "While running Docker containers as root it not recommended, those running in this way should be aware that the container runs as user "nobody" by default. This will potentially cause permissions errors in certain deployment environments."
The text was updated successfully, but these errors were encountered:
I'd like to suggest that the default docker user id being assigned as 'nobody' be mentioned somewhere in the docker installation documentation.
This is breaking for some installation configurations (mine: small experimental lab with Portainer as root, which results in a container that looks running but isn't actually working...my level of frustration at struggling fo 2 hours to figure out why a container wont deploy, only to find an issue 7 years old, but undocumented without digging into git to find it.....)
I don't have the requisite experience or time to make a pull request on this.
My thought would be to use language like this: "While running Docker containers as root it not recommended, those running in this way should be aware that the container runs as user "nobody" by default. This will potentially cause permissions errors in certain deployment environments."
The text was updated successfully, but these errors were encountered: