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

[Error] incorrect ownership for directories copied from /etc/skel #1612

Open
befanyt opened this issue Nov 11, 2024 · 0 comments
Open

[Error] incorrect ownership for directories copied from /etc/skel #1612

befanyt opened this issue Nov 11, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@befanyt
Copy link

befanyt commented Nov 11, 2024

Please, before opening a bug:

  • make sure you've read the documentation.
  • Ensure there isn't already an open issue about this.
  • Ensure there isn't already a closed/resolved issue about this.

Describe the bug
When you have a file instead of subdirectory of skel, eg /etc/skel/.config/foobar, the file itself (foobar) gets copied with correct ownership (1000:1000), but its parent folder (.config) is owned by root, meaning that other program's can't write to it.

To Reproduce
Use any image which includes files in subdirectories of /etc/skel

Expected behavior
The directory is owned by 1000:1000

Logs
Run the commands with --verbose and post the log here as a file upload
Attach also the output of podman logs or docker logs, possibly with --latest flag

Desktop (please complete the following information):

  • Are you using podman, docker or lilipod? podman
  • Which version or podman, docker or lilipod? 5.2.3
  • Which version of distrobox? 1.18.0.1
  • Which host distribution? Bluefin (Fedora Silverblue)
  • How did you install distrobox? Bluefin provided

Additional context
Seems that this issue occured earlier #1144 and got fixed, then got another implementation after #1317 and the same issue shows up again.
distrobox.log

@befanyt befanyt added the bug Something isn't working label Nov 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant