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

[BUG] Changes owner of mounted volume to the /config #29

Closed
1 task done
isumix opened this issue Jun 16, 2024 · 2 comments
Closed
1 task done

[BUG] Changes owner of mounted volume to the /config #29

isumix opened this issue Jun 16, 2024 · 2 comments

Comments

@isumix
Copy link

isumix commented Jun 16, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

Currently shown in the example to mount into container's /config
But this will chown -R anything mountend into this directory with the PUID:PGID

Expected Behavior

Either rewrite docs (README) recommending other location and warning about this behavior.
Or fix this behavior.
Mounted files` permissions must not be changed.

Steps To Reproduce

As a normal user (not root), run the command below, mounted folder will be chown-ed

Environment

- OS: Debian 12.5
- How docker service was installed: apt-get install podman

CPU architecture

x86-64

Docker creation

podman run -d \
  `# Mounting anything within /config will chown -R` \
  -v "${HOME}/Projects:/config/Projects" \
  "docker.io/linuxserver/openvscode-server:1.90.1"

Container logs

usual
@j0nnymoe
Copy link
Member

This isn't a bug. The container expects to have control over the /config and set it to the PUID/PGID provided otherwise it sets to 911 for both.

@aptalca
Copy link
Member

aptalca commented Jun 16, 2024

  1. As J0nnymoe stated, /config is the container's folder and the container manages its permissions.
  2. /config/workspace is where the container expects the project files and that folder is excluded from permission fixing
  3. We expect the user to map the /config folder, not some random subfolder to it

@aptalca aptalca closed this as not planned Won't fix, can't repro, duplicate, stale Jun 16, 2024
@LinuxServer-CI LinuxServer-CI moved this from Issues to Done in Issue & PR Tracker Jun 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

No branches or pull requests

3 participants