Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Subject requirement regarding Docker solution #69

Open
linhtng opened this issue Aug 30, 2024 · 0 comments
Open

Subject requirement regarding Docker solution #69

linhtng opened this issue Aug 30, 2024 · 0 comments
Assignees

Comments

@linhtng
Copy link
Contributor

linhtng commented Aug 30, 2024

I just read this in Luis comment on Rasmus's team:
Image

I believe he is refering to the red box in Subject page 5 which said:

If your container solution is Docker:
When your computers in clusters run under Linux, you will use Docker
in rootless mode for security reasons. This comes with 2 sideways:
• Your Docker runtime files must be located in /goinfre or /sgoinfre.
• You can’t use so called “bind-mount volumes” between the host and the container if non-root UIDs are used in the container.
Depending on the project, your situation and the context, several
fallbacks exist: Docker in a VM, rebuild you container after your
changes, craft your own docker image with root as unique UID.

Now, I'm real worried about the part in Luis comment that "we agreed that it's fine as long as there are no bind mounts from the users computer to the actual docker containers" because we do have such bind mounts in compose.yml file. I'm still not sure wtf the subject wants really. But if our evaluator is like Luis, then we're fucked.

Can you please ask around, figure out, fix this if needed and all in all make sure we are not failing on this point?
@liocle @djames9

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants