BoxBuddy Stuck on starting container
Is this a known issue? Not sure where to look for logs if any.
Solution:Jump to solution
Boxbuddy doesn't have an option for adding additional packages when doing an installation which is usually needed for the "init" stuff so try something like this in the terminal when creating the distrobox
distrobox create --name debian-test --image debian:latest --init --additional-packages "systemd" The key parts are --init and --additional-packages "systemd"6 Replies
It's normal for it to sit on starting container for about 10 minutes or longer. The first setup takes forever. After that it's pretty quick to start up
I forgot to mention this was with an already setup box I've used multiple times before. That being said after a reboot I got it to recreate the box and it's working as intended it seems for the most part
Does systemd not work right now by chance cause I feel that may have been my issue.
Solution
Boxbuddy doesn't have an option for adding additional packages when doing an installation which is usually needed for the "init" stuff so try something like this in the terminal when creating the distrobox
distrobox create --name debian-test --image debian:latest --init --additional-packages "systemd" The key parts are --init and --additional-packages "systemd"Distrobox as a whole sometimes get stuck during
ujust update. Mentions something about a .fifo missing in .cache. A retry usually does the trick
I presume this is somewhat related…?it might be getting stuck because it can't log in to do the updates. No idea if that related though
I ended up just using gnome boxes (libvirt) to do what I need for now but would love to move back to using a container - I'll checkout what you posted next time I go to mess with distrobox/boxbuddy some more, thanks again @wolfyreload and @Linus Xu !!