You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
Please, before opening a bug:
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 uploadAttach also the output of
podman logs
ordocker logs
, possibly with--latest
flagDesktop (please complete the following information):
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
The text was updated successfully, but these errors were encountered: