kDE-neon 20.04 doesnt work with the new release but works flawlessly with CUBIC Classic. Issue with kDE-neon in Cubic Release is with dns resolv.conf and being able to ping 8.8.8.8 but not being able to update with APT or PackageKit.

What is the OS/Distro on the host machine that you are running Cubic on?

kDE neon. 20.04. with kernel 5.8.
Intel i7. 16G. Ram. SSD. HP desktop.
Full disk. Single OS install.

kDE neon. 20.04. with kernel 5.8.
Intel i7. 16G. Ram. SSD. HP desktop.
Full disk. Single OS install.

OK, I'll take a look at this scenario:

    KDE Neon running Cubic to customize KDE Neon

For background, there is a problem with the container implementation in Debian which makes networking not work in containers.
To work-around this, Cubic mount the host's resolv.conf file (as read only, of course).
(This file is actually a sym-link on the host system: /etc/resolv.conf -> /run/systemd/resolve/stub-resolv.conf)

There may be some nuances unique to Neon or KDE that make this work-around ineffective.

Nevertheless, there should be a manual work-around you can do.

Thanks for the quick reply.
Sorry I forgot to include in my original post that I implemented the resolv.conf work around but the Cubic custom ISOs always failed on installation. I couldnt tell you if the issues were related. sorry
The last time I used CUBIC release it kept chrooting to the host system.

Cubic Classic works perfect for kDE-Neon.

Happy days
Thanks again

Hunter,

I was able to get DNS lockups working in Cubic by doing the following on the HOST system PRIOR to launching Cubic:

    $ sudo mv /etc/resolv.conf /etc/resolv.conf.original
    $ sudo ln -s /run/systemd/resolve/stub-resolv.conf /etc/resolv.conf

In this way, I did not need to change anything in Cubic's Terminal.

I will attempt to create a customized ISO and let you know what I encounter.

Hunter,

I was able to create a custom ISO and install it...

(1)
I installed Neon in VirtualBox using neon-user-20201001-0946.iso.

(2)
I booted into Neon in VirtualBox and installed Cubic.

(3)
Before launching Cubic, I executed the following commands to make sure DNS lookups would work inside Cubic:

    $ sudo mv /etc/resolv.conf /etc/resolv.conf.original
    $ sudo ln -s /run/systemd/resolve/stub-resolv.conf /etc/resolv.conf

(4)
I started Cubic and navigated to the Terminal page.

(5)
I successfully tested DNS by typing:

    $ ping google.com

(6)
As a simple customization, I installed only one package:

    $ apt install tree

(7)
I navigated to the Generate page in Cubic to create a new custom ISO.

(8)
I exited Virtual Box, and selected the new custom ISO as the boot medium.

(9)
I successfully tested DNS from the custom Live ISO by typing:

    $ ping google.com

I then installed the customized OS in Virtual Box.

I did not encounter any errors during installation.

(10)
I booted into the custom OS in Virtual Box.

I successfully tested DNS in the installed OSby typing:

    $ ping google.com

I successfully verified that my customizations were present in the installed OS:

    $ tree

Thus, the trick to getting DNS to work in Cubic when Neon is the host OS, is to...

Execute the following on the HOST system PRIOR to launching Cubic:

    $ sudo mv /etc/resolv.conf /etc/resolv.conf.original
    $ sudo ln -s /run/systemd/resolve/stub-resolv.conf /etc/resolv.conf

(This desn't seem to adversely affect the host system, but you can always revert to the original resolv.conf).