Distrobox in distrobox confusion

[paul-hammant]

What I did:

On a host of Ubuntu 22.04 with podman.

I've done distrobox enter test --name levelOneTest

That's a Fedora:39 today.

Where I tripped up

In the Fedora client I did the curl-pipe-to-sudo-shell install distrobox again, but it barfs on not having the privileges to change files in /usr/local/share/icons/hicolor/scalable/apps/ on the Ubuntu host.

Well, I'm happy with it not being able to do that, but I'd be wanting it to not try at all.

Where my experience of Distrobox is south of everyone else's

Is there a --dontUseHostFileSystem equivalent argument for compete FS sandboxing?

I realise there were different limitations for Docker than Podman, so deliberately chose podman as a dep to experience this implicit nesting of containers. I was doing to change it up as I went deeper - Ubuntu:22 containing Fedora:39 containing Debian:12 containing a NixOS or something else. I was going to name them to make it clear to me where I was in that at any one time. I didn't get very far, as you can see.