Docker0 in sys-net

Why is docker0 in sys-net here?

user@sys-net:~$ ip -s link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    RX:  bytes packets errors dropped  missed   mcast           
          3712      52      0       0       0       0 
    TX:  bytes packets errors dropped carrier collsns           
          3712      52      0       0       0       0 
3: vif80.0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group 2 qlen 1000
    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
    RX:  bytes packets errors dropped  missed   mcast           
    2128142243 1994292      0       0       0       0 
    TX:  bytes packets errors dropped carrier collsns           
    5223163711 2436343      0       0       0       0 
4: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default 
    link/ether 02:42:e4:60:e8:19 brd ff:ff:ff:ff:ff:ff
    RX:  bytes packets errors dropped  missed   mcast           
             0       0      0       0       0       0 
    TX:  bytes packets errors dropped carrier collsns           
             0       0      0       2       0       0 
6: ens6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
    link/ether 08:bf:b8:19:a0:2e brd ff:ff:ff:ff:ff:ff
    RX:  bytes packets errors dropped  missed   mcast           
    1302228532 1041025      0    7080       0      69 
    TX:  bytes packets errors dropped carrier collsns           
     312488375  469725      0       0       0       0 
    altname enp0s6
    altname enx08bfb819a02e

Did you modify the template?

Only good reason I see is docker being installed in that template.

Hmm… oh man… thanks! Yeah, I’ve dabbled with Docker before. I need to set up Qubes OS from scratch again.

no, just remove and re-install the template. And stop modifying the original templates from Qubes OS, clone them and work with those.

Yeah, I’ll do that as soon as I have more hard drive space. That’s the main reason why I’m always fiddling around with TemplateVM.

Not sure what you’re doing but they shouldn’t take up that much space.

How much space do you have? I highly doubt its because of template VMs.

Every time a template is cloned, its “content” is also cloned.
In Qubes Manager, the disk usage is displayed under “Disk Usage.”
If I clone a 5GB template, the clone also uses 5GB.
If I create 10 clones, my templates alone will use 50GB.

Also I’d recommend to just use debian-13-minimal, no need to have this “everything installed” template for the VM that just runs one application (kuhbs does it like this, it always starts from scratch).

No:

Ok, fair port.

Then wait for kuhbs, it uses the debian minimal template and does all the management for you :wink:

But I miiiiiiight switch to kicksecure still, not sure yet. I very very much want to.

But yeah, fair, just use the -xfce templates, they do make everything simpler. Absolutely true.

Love adw’s post there btw.. Some quotable things for the website like the 80/20 thing..

@kuhbs I’ve posted a new entry here:
https://forum.qubes-os.org/t/template-debian-minimal-vs-kicksecure/42547