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
I am running distrobox 1.4.2 on a Debian 12 system, I'm running Ubuntu 18.04 in a container to provide a legacy python 2.7 environment.
There is one significant annoyance, the container files down in ~/.local/share/containers aren't all readable by the user where they have been installed. Thus whenever I issue a 'find' command I get a whole crop of permission denied messages which often rather overwhelm what I'm looking for.
Could there be a configuration option to set the directory for the container data? Then I could put it in /var or somewhere like that. Alternatively, is it really necessary to have the files owned by (non-existent) user 100000, can they not be owned by the installing user?
The text was updated successfully, but these errors were encountered:
I have overcome this problem by using ACLs (setfacl command) so that I can read the files in spite of the basic permissions/ However I still think this issue needs to be fixed somehow.
I am running distrobox 1.4.2 on a Debian 12 system, I'm running Ubuntu 18.04 in a container to provide a legacy python 2.7 environment.
There is one significant annoyance, the container files down in ~/.local/share/containers aren't all readable by the user where they have been installed. Thus whenever I issue a 'find' command I get a whole crop of permission denied messages which often rather overwhelm what I'm looking for.
Could there be a configuration option to set the directory for the container data? Then I could put it in /var or somewhere like that. Alternatively, is it really necessary to have the files owned by (non-existent) user 100000, can they not be owned by the installing user?
The text was updated successfully, but these errors were encountered: