Unable to use docker in distrobox
I am trying to install CasaOS via distrobox since its not supported on fedora. at first i get a permissions issue, then i get a docker daemon not running error
21 Replies
Have you looked at this? https://github.com/89luca89/distrobox/blob/main/docs/useful_tips.md#using-docker-inside-a-distrobox
GitHub
distrobox/docs/useful_tips.md at main · 89luca89/distrobox
Use any linux distribution inside your terminal. Enable both backward and forward compatibility with software and freedom to use whatever distribution you’re more comfortable with. Mirror available...
checking it ou
t
completely forgot i asked for help
but uh
i didnt get it working
i instead tried debian instead of ubuntu in distrobox as that was more supported for casaos, and it failed on another step to do with casaos not starting a certain casaos service
i asked help in the server for casaos and got told that its probably due to distrobox being a virtualization layer
considering im supposed to install things in distrobox on bazzite, and considering that casaos isnt even supported on fedora, that means i cant disregard the first part.
so leads me to believe that i just cant do it on fedora
Distrobox is not a virtualization layer
But you trying to run a container engine inside a container
is that not possible
i looked up container in a container and saw podman as being used to make nested containers
but i assume that making an alias from docker to podman wouldnt be as easy as that
no it was not
the casaos-gateway.service isnt running but since i didn't even get help in their server I'ma just wait until i get a device just for this probably soon
i know it works on my laptop but I'm not gonna use that for this
it actually blew my mind opening my browser in my browser thru casaos
fun quirk: it appears that you need a browser installed in the distrobox container to access the casaos server
did you follow the instructions on how to install debian with init and also make a rootful box?
I pieced it all together from the distrobox docs and also the docker-ce docs
Docs used:
for Debian install instructions:
https://github.com/89luca89/distrobox/blob/main/docs/useful_tips.md#using-init-system-inside-a-distrobox
for additional flags
--root --unshare-all
https://github.com/89luca89/distrobox/blob/main/docs/useful_tips.md#using-docker-inside-a-distrobox
for installing Docker
https://docs.docker.com/engine/install/debian/
for installing CasaOS
https://casaos.io/
yes i did both
init and additional
and i first installed docker thru their preferred method, the script they provide. then i did the casaos script and it fails on my error
i am trying again right now tho
JUST IN CASE i somehow messed up
distrobox create --root --image debian:12 --name debian --init --unshare-all --additional-packages "systemd libpam-systemd podman"
tray@bazzite:~$ distrobox enter --root debian
Starting container... [ OK ]
Installing basic packages... Error: An error occurred
well i didnt even get that far ;/
$ distrobox create -i debian:stable --init --additional-packages "systemd libpam-systemd pipewire-audio-client-libraries" -n casabian --root --unshare-all
don't know why you'd be installing podman into the container because the point is to run docker
all but the last two arguments of that command came from the section about using init systemtbh
that was a remnant of me trying different things to get it working
unsure if it was your command or me rebooting my system that got it to install the stuff it needed to start
installing casa now
lets hope
sigh
i mustve missed something before
fun
it's running at port 80 by default
see above for browser info
there's probably a way to expose it outward, but I didn't look hard enough
I feel like I have done enough work for you
i have tailscale
I meant expose from the container to the host
ah
the host cannot see the server by default. there's likely a command or configuration that lets this happen
i think i saw that earlier\
hey thanks for all of the help!
to get it working i had to remake the container with the port 1234
(cuz 8080 was already taken, i think cuz of syncthing)
i scrapped it all and formatted my other pc and slapped Ubuntu on and and it's working