Due to a recent containerd 1.7.24 update, your /dev/net/tun:/dev/net/tun mapping needs to be moved from the volumes section to the devices section.
Don't be like me and realize this AFTER you leave home for the holidays.
Heads-Up for anyone running Tailscale via docker-compose (Breaking Change)
https://github.com/tailscale/tailscale/issues/14256
9 Comments
AtariDump@lemmy.world · 6 pts · 1y
Let this be a lesson to implement a change freeze 1 week before leaving home for a holiday/trip/etc. 😁
RxBrad@infosec.pub · 1 pts · 1y
Luckily I realized that I could Cloudflare-tunnel my Portainer UI out to a long random-nonsense subdomain name.
That allowed me to fix it (and then immediately kill the tunnel -- not a fan of exposing Portainer to the internet).
RxBrad@infosec.pub · 4 pts · 1y
Adding this device this also appeared to fix my https://github.com/haugene/docker-transmission-openvpn container that recently died. (And not simply giving it elevated privileges, as was previously recommended)
https://github.com/haugene/docker-transmission-openvpn/issues/2883
It appears that these issues all originate from an update to runc (which is used by containerd): https://github.com/containerd/containerd/issues/11078
Cpo@lemm.ee · 3 pts · 1y
Thank you for your sacrifice. It will not be forgotten.
c2c2@lemmy.world · 3 pts · 1y
Kind of crazy it wasn't like this from the start.
Appoxo@lemmy.dbzer0.com · -2 pts · 1y
Luckily my stack is only auto updating every month and only my downloader was impacted by this breaking change.
kitnaht@lemmy.world · -7 pts · 1y
This is the kind of bullshit I don't have time for, when shit gets broken in userspace because someone wanted to change the location of something.
Appoxo@lemmy.dbzer0.com · 13 pts · 1y
Makes sense to move it where it's appropriate.
Scipitie@lemmy.dbzer0.com · 7 pts · 1y
No one forces unattended updates. And containerd is already living in the userspace.
If every dev would live on a kernel level stability approach we'd will not have a containerd release at all.