glizzyguzzler

Thanks for taking the time to reply!

The host setup has eth0 as the physical interface to the rest of the network, with br0 replacing it completely. br0 has the same MAC as the eth0 interface and eth0 just forwards to br0 which then does the bridging internally. br0 being a bridge means that incus is able to split it off without MACVLAN but rather its nic device in bridge mode which "Uses an existing bridge on the host (br0) and creates a virtual device pair to connect the host bridge to the instance." That results in a network interface that has its own MAC and is assigned a local IP by the DHCP server on the network while also being able to talk to the host.

Incus accomplishes the same goal as Proxmox (Proxmox has similar bridge network devices for its containers/VMs) just without Incus needing to be your OS/distro like Proxmox does, it's just a package.

As for the Docker, the parent interface is br0 which has supplanted eth0. MACVLAN is working as it is intended to in Docker, as far as I can tell. The container has a networking device with its own MAC address, and after supplying the MACVLAN network device with my network's subnet and gateway and static IP address in the Docker compose file it works as expected. If I don't supply a static IP in the Docker compose file, Docker just assigns it the first IP in the given subnet - no DHCP interaction. This docker-net-dhcp plugin (I linked to the issue about it not working on the latest version of Docker anymore) was made to give Docker network devices the ability to use DHCP to get an IP address, but it's clearly not something to rely on.

If I'm missing something about MACVLAN that makes DHCP work for Docker, let me know! Hardcoding an IP into a docker-compose file adds an extra step to remember compared to everything else being configured on the centralized DHCP server - hence the shoddy implementation claim for Docker.

Thanks for the link to using another MACVLAN and routing around the host<-/->container connection issue inherent to MACVLAN. I'll keep it in mind as an alternate to Incus container around another container! I do wish there could be something like Incus' hassle-free solution for Docker or Podman.

Not what you asked for but possibly useful; if you have apple devices and can use airplay instead of Bluetooth, https://github.com/mikebrady/shairport-sync works really well. Even runs airplay 2 on a pi zero smoothly. Don’t know of Bluetooth otherwise sadly

Mmm hitting a reviewer with “out of scope😎😎😎” feels so good

More research is required straight into my veins every time

this got alt acc vibes, def too crabbo to be a coincidence. Perp up top got it right

Glue the switch, transcend beyond turning off your robo vac

I believe they meant “lobes” as in “they don’t have the lobes to conduct business” a common accusation in the Ferengi culture

/s, probably

Based O’Brien would engineer a thousand-round 3D printed gun while the federation’s ATF just weeps in a corner

Info dump info dump info dump straight in my veins

Christian religions refer to followers of their religion as “children” and their god as “father”, hence the phrasing. If you’ve grown up in a region that is Christian-dominated it’s regular phrasing. Also jesus is also god or something idc and priests are father too probably

Embedded image babyyy

You can’t have like two pics to flip between afaik so I went with embedding the secret surprise upgrade after reeling in peeps with the main pic

I’m not suggesting the mass media coverage of things that are super clearly airplanes and helicopters yet the journalists give it a “I can’t see the American livery, run the same story again!” is clearly bad faith journalism to try to drown out support for a class war, I’m saying that’s what it is

My friends hit each other with nasty crusty aged copypasta on the reg, and I just blasted this bad boy before I came here