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
When Testbed scenarios are run in Docker, logs and files are owned by root. This is a well-known Docker issue (see: docker/for-mac#5480, where it is mentioned the same thing happens on WSL)
It seems that files get the same UID and permissions on the host as they were given in the image. Thus if the Docker runs as root, then the host owner will also be root. A possible workaround is to create a corresponding user (with same UID) in docker, but this a little finicky -- especially across platforms.
An alternative solution is to just make sure the files are world-writable, so that the non-root users can manage the outputs.
The text was updated successfully, but these errors were encountered:
When Testbed scenarios are run in Docker, logs and files are owned by root. This is a well-known Docker issue (see: docker/for-mac#5480, where it is mentioned the same thing happens on WSL)
It seems that files get the same UID and permissions on the host as they were given in the image. Thus if the Docker runs as root, then the host owner will also be root. A possible workaround is to create a corresponding user (with same UID) in docker, but this a little finicky -- especially across platforms.
An alternative solution is to just make sure the files are world-writable, so that the non-root users can manage the outputs.
The text was updated successfully, but these errors were encountered: