Ok. This is good news, we've found the problem.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
For a short term solution, you ~should~ be able to create /etc/resolv.cof inside Cubic (after deleting the symlink), and add the exact same contents from the /etc/resolv.conf on your host system.
On my Kubuntu 21.04 host, resolv.conf is actually a symlink to an existing file:
/etc/resolv.conf -> ../run/systemd/resolve/stub-resolv.conf
Do you know why that is not the case for you?
(I'll also look into this a bit more on my end also; Cubic should handle this kind of situation).
Ok. This is good news, we've found the problem.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
For a short term solution, you ~should~ be able to create /etc/resolv.cof inside Cubic (after deleting the symlink), and add the exact same contents from the /etc/resolv.conf on your host system.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
On my Kubuntu 21.04 host, resolv.conf is actually a symlink to an existing file:
/etc/ resolv. conf -> ../run/ systemd/ resolve/ stub-resolv. conf
Do you know why that is not the case for you?
(I'll also look into this a bit more on my end also; Cubic should handle this kind of situation).