My host system is connected to the Internet just fine, but commands from within the container cannot access the Internet.
~> curl google.com
curl: (6) Could not resolve host: google.com
~> host-shell curl google.com
<HTML><HEAD><meta [...]
#[Solved] No internet in vso-pico container
iron hull
flat harbor
The vso-pico container uses --network=host, so that should not be an issue. I wonder if you are using any custom DNS configurations.
marble forum
Rebooting should restore the connection
iron hull
is there any way other than rebooting?
feral girder
Have this issue too. ping google.com fails but ping 8.8.8.8 works fine host-shell ping google.com works fine too. Lol?
iron hull
next time i get the problem (i have rebooted since this was opened), i will try 8.8.8.8
quaint field
is there any way other than rebooting?
You can right click BlackBox, open a Rescue Mode Terminal and run:
/usr/share/apx/distrobox/distrobox stop apx-vso-pico
(You can also run that with Alt+F2 or a keyboard shortcut)
Note that it will kill everything that's currently running in the vso container
tall oar
Yes. I do that directly from within apx-vso-pico, when I switch from one network to another, to get internet access back.
host-shell /usr/share...
That kills the shell of course, afterwards I click on the blackbox icon in the GUI and apx-vso-pico is started again as on first access after system startup.
quaint field
could this be run in a regular terminal session with host-shell?
I would recommend against it. It will kill the process that's currently stopping the container.
This sounds like something that could lead to containers going into a broken half-stopped state or data corruption if you're very unlucky.
iron hull
ah, that makes sense. thank you!
round cradle
You can fix it also with a remount command, sending it later here once I'm in office
round cradle
@iron hull @feral girder
sudo umount /etc/resolv.conf
sudo mount --bind /run/host/etc/resolv.conf /etc/resolv.conf
The issue you are experiencing is that it doesn't update the dns server once you change networks, this should fix it
iron hull
Good to know, thanks