Distrobox failing to start box
I've uploaded the
distrobox enter parrot-os -v log. Here's the distrobox.ini file:
74 Replies
@tulip I ping you due to you mentioning in the past that I can ping you for help, but don't take it as a rush request š
Maybe try this with the /var/home instead of the symbolic link of just using /home
trying now. It did successfully create the location and put stuff in it, but maybe only part of the process respects symlinks for whatever reason
I've seen weird things before with symlinks. Might or might not work but it's it's simple to try
yep simple to try, but didnt work
same error, not a new one
sending a message here so i remember to check this
im out noe, ikl answer this later
@Raevenant what is exactly your issue?
i think its something to do with the base image, do you mind testing out some other one? like, just change the base to
ubuntu:latest on your distrobox.iniYeah gimme a min
ok yeah it's the base image that isn't working. Is distrobox not able to use all docker images as bases?
so it's weird too, because I can enter the container just fine with
-it flags just using podman itself, so idk what distrobox puts on top of all that
actually tbh, I don't think I want parrot running as a distrobox lmao I actually want the sandboxing that distrobox works around
Actually ignore that š there are still good reasons to use distro box for this, so if youve got any ideas for how to make it work, I'm all ears
It works just fine when I run it with podman -it and I can mount volumes n stuff, so idk why distrobox specifically doesn't work
Oh, I never answered this, my b. It assembles just fine, but when I do distrobox start parrot-os it fails towards the end and can't finish setting up the box
However as mentioned, if I run it directly, it runs just fine. However some of the niceties that distrobox gives like re-assembling with a command would be super helpful
oh but running it with podman run -it doesn't save anything installed the way that distrobox does, so I actually do need to figure this outi think the parrotOS image has some /etc/profile.d hook that makes it so you cant login to the distrobox
im sorry i was out all day today
and yesterdayh
lemme see if i can reproduce your issue
also, you can add some sandboxing if you want to on distrobox
that would be awesome too
i do this on my distroboxes
distrobox create fedorabox -Y --no-entry --unshare-process --unshare-devsys --image registry.fedoraproject.org/fedora:rawhide --addit
ional-packages "git git-delta just nu helix meson clang ccache "my ideal scenario would be to put it back to fully sandboxed, but with a volume so I can put files into the box
oh you absolutely can do that
just unshare everything but
netnsI assume all of those flags can be put someplace in the
distrobox.ini too ye?no idea, never used those on distrobox assemble š
lemme see
yup
awesome
i highly recommend doign unshare_devsys if you are doing something funky
what's it do?
I'm almost always doing something funky š
it shares your devices to
/dev on the distrobox
/dev/sda...
dd if=image of=/dev/sda would workoh! Ok, I haven't done anything that funky, but that's good to know
you know whats funny, podman has a lot more namespaces but distrobox doesnt expose them
podman, that being the linux kernel actually
wait wait wth
@tulip using your flags worked what the hell
The Sigma
THIS IS SO FUNNY THO WHY DID IT WORK LMAO
distrobox create parrotsec -Y --no-entry --unshare-process --unshare-devsys --image parrotsec/security:latest
that works@Niklas ā” another thing fixed without me doing shit.
its the magical hands
LMAO
see
i told you
š¤£
GALINHA WHATSAPP
LES GOOOOOOOOOOOOOOOOOOO
look, we all know that in the world of software and engineering, the tech only respects whichever technomancer has the highest level
tulip just had to stare at my machine and glare it into submission š
we call it the "magic hands"
fixed an issue of mine too
lmao
you know, if it works it works
yeah lol
dude @tulip I can't reproduce it now either at all
it literally wasn't your flags, it was just you watching š
LOL
@Niklas ā” even better now
theres no way LOL
like why did it not work before
beats me, it's mega weird
you can check the logs with
podman logs parrothingI'm trying with one more flag
aight lets see
the only flag left is the
home oneSolution
YO it's the
home oneok, so what ways are there to sandbox this properly then?
i wonder whats goin on then?
apparently moving
home breaks something
cause like, it doesn't sandbox when you do that, it just moves itif you want to truly sandbox this you can run it as a different user all together
so maybe some links or smth are breking
what you think?
yeh, lets try a full sandbox and see what happens
do
useradd mynewuser
then sudo -u mynewuser distrobox assemble -f whatveroh shoot, like a new user on my host?
the new user wont have access to your home tho
yes.
hmmmmmm
is there a way to make distrobox act otherwise like a normal container? Sandboxed, but without access to /home/ or anything else?
I'd like to be able to mount a volume that's in my user's home
why dont you just run a normal container then?
it dissappears when I exit out
podman create mycoolthing with the image
you are running it with podman --rm
podman ps -a should show it if you arent running with rmno, I mean any changes I make don't stick around
if I install programs, etc
are you on bazzite?
ye
damn
this would be the perfect time to use incus
what's incus?
stateful containers like distrobox
but without podman
its more made to actually work statefully
oh huh
you can use
systemd-nspawn on bazzite tho
i think i know what we can do
mind creating a $HOME/machines folder?yeah sure
also maybe this should be a separate thread?
this is showing up publically on answeroverflow LOL
maybe a thread in #š®bazzite
OH LMAO
what happened?
nono, just I didn't know this was all public outside discord lmao
YUP