8000 Bind mounts and root-owned files · Issue #99 · exekube/exekube · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
This repository was archived by the owner on Jun 17, 2023. It is now read-only.
This repository was archived by the owner on Jun 17, 2023. It is now read-only.
Bind mounts and root-owned files #99
Open
@mrtyler

Description

@mrtyler

Hi Ilya,

In the interest of contributing our changes back to upstream, I wanted to tell you about a problem we encountered and how we solved it. It happens outside of the normal exekube flow, so I'm creating an Issue rather than a PR.

I described the problem here, including links to upstream docker/docker-compose Issues:
gpii-ops/gpii-infra#80 (comment)

(Note that this does not affect Docker for Mac, which is probably why none of us noticed it until we tried to run exekube on our (Linux) CI machine. ;))

We ended up abandoning the "run as a non-root user inside the container" strategy described there. Instead, we moved from bind mounts to Docker Volumes (in particular, see docker-compose.yaml):
gpii-ops/gpii-infra#92

This might not be a good fit for exekube / exekube demo projects since it requires some extra stuff outside of exekube to manage Docker Volumes, but I wanted to let you know about it. Feel free to close this Issue without further action.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0