fixuid VS nsenter

Please check the following: https://docs.docker.com/storage/bind-mounts https://docs.docker.com/storage/volumes https://en.wikipedia.org/wiki/User_identifier (Unix-like operating systems identify a user by a value called a user identifier...) https://stackoverflow.com/q/23544282/5113030 (What is the (best) way to manage permissions for Docker shared volumes?...) https://stackoverflow.com/q/29245216/5113030 ((Bind-mounted) volumes in Docker will maintain the permissions that are set on...) https://stackoverflow.com/q/34031397/5113030 (Running docker on Ubuntu: mounted host volume is not writable from container...) https://stackoverflow.com/q/44683119/5113030 (Dockerfile replicate the host user UID and GID to the image...) https://boxboat.com/2017/07/25/fixuid-change-docker-container-uid-gid (Introducing fixuid: Tool for Changing Docker Container UID/GID at Runtime...) https://github.com/boxboat/fixuid (fixuid is a Go binary that changes a Docker container's user/group and file permissions that...)

FROM registry.gitlab.haskell.org/ghc/ci-images/x86_64-linux-deb10:0849567cd9780cc8e9652118b949cb050c632ef4 ARG UID ARG GID RUN \ curl -SsL https://github.com/boxboat/fixuid/releases/download/v0.5.1/fixuid-0.5.1-linux-amd64.tar.gz | sudo tar -C /usr/local/bin -xzf - && \ sudo chown root:root /usr/local/bin/fixuid && \ sudo chmod 4755 /usr/local/bin/fixuid && \ sudo mkdir -p /etc/fixuid && \ printf "user: ghc\ngroup: ghc\n" | sudo tee /etc/fixuid/config.yml USER ${UID}:${GID} RUN fixuid USER ghc RUN \ sudo rm -r \ /etc/fixuid \ /usr/local/bin/fixuid \ /var/run/fixuid.ran ENV PATH=${PATH}:/home/ghc/.cabal/bin:/opt/ghc/9.2.2/bin RUN \ sudo apt update && \ sudo apt install -y \ bash-completion && \ cd /tmp && \ git clone https://github.com/haskell/haskell-language-server.git && \ cd haskell-language-server && \ cabal --project-file=cabal-ghc92.project update && \ cabal --project-file=cabal-ghc92.project install && \ rm -rf /tmp/*

For the local development scenario, I made an open source utility that uses the setuid bit to change the UID/GID of a particular user and any files that user owns inside of the container at runtime:

https://github.com/boxboat/fixuid

You can also look at adding fixuid to the container: https://github.com/boxboat/fixuid

You can browse these devices like any other physical storage device. If it's attached to a host, you can ssh to the host (or use a tool like nsenter: https://github.com/jpetazzo/nsenter/blob/master/README.md ) to browse the filesystem. PVs can be ebs volumes, NFS volumes, gluster volumes, local directories, and a whole host of other options: https://kubernetes.io/docs/concepts/storage/persistent-volumes/#types-of-persistent-volumes

This one liner enters the namespace of Rootless Docker, and does the chown back to your normal user (root is your host user when you switch back to your namespace).

Anytime you use overlay filesystem ... like storing database on disk so docker doesn't kill it every run, this is useful. So you can do backups, rebuild docker images, etc.

More information: https://github.com/jpetazzo/nsenter#how-do-i-use-nsenter