Creating a bug report/issue
I have searched the existing open and closed issues
Required Information
-
DietPi version |
cat /boot/dietpi/.version
G_DIETPI_VERSION_CORE=9
G_DIETPI_VERSION_SUB=12
G_DIETPI_VERSION_RC=1
G_GITBRANCH=‘master’
G_GITOWNER=‘MichaIng’ -
Distro version |
echo $G_DISTRO_NAME $G_RASPBIAN
bookworm -
Kernel version |
uname --all
Linux OPI 6.1.115-vendor-rk35xx #1 SMP Thu May 1 16:13:28 UTC 2025 aarch64 GNU/Linux -
Architecture |
dpkg --print-architecture
arm64 -
SBC model |
echo $G_HW_MODEL_NAMEor (EG: RPi3)
Orange Pi 5 Plus (aarch64) -
Power supply used | (EG: 5V 1A RAVpower)
5v 4a -
SD card used | (EG: SanDisk ultra)
boot on SD, data on M.2
Additional Information (if applicable)
-
Software title | (EG: Nextcloud)
Peertube on docker with IPV6 -
Was the software title installed freshly or updated/migrated?
Nope. I have the problem since I changed my internet provider. Its router now comes with ipv6 public ip instead of ipv4 public ip. So I had to reconfigure my hosted services to use the public IPv6. -
Can this issue be replicated on a fresh installation of DietPi?
Yes, in fact I have two locations, a RP4 and OPI5+, and both with the same behavior. -
Bug report ID |
echo $G_HW_UUID
?
Steps to reproduce
- Having a global IPv6 on the SBC
- Having a reverse proxy listening on ipv6
- Starting Peertube Docker Container
Expected behaviour
- Enjoying Peertube
Actual behaviour
- All my services become unavailable
- This comes down to IPv6 configuration of SBC, which loses “global IPv6”.
Extra details
From my little experience, I believe the SLAAC lease duration is perticularly short. But I have no idea how to definitively increase this. And I’m not sure it’s the only problem.
Here is my conf before starting peertube :
3: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether c0:74:2b:ff:6a:2e brd ff:ff:ff:ff:ff:ff
inet 192.168.1.3/24 brd 192.168.1.255 scope global dynamic eth0
valid_lft 71663sec preferred_lft 71663sec
inet6 2a02:8429:8331:7e01:c274:2bff:feff:6a2e/64 scope global
valid_lft 493sec preferred_lft 493sec
inet6 fe80::c274:2bff:feff:6a2e/64 scope link
valid_lft forever preferred_lft forever
Once Peertube is loaded, the “global” disappears.
EDIT : I resolved the problem months after my post by changing the way I use ipv6 on docker.
Docker was never built to do ipv6, support is kind of experimental, moreover it doesn’t support ipv6 the same way it supports ipv4, meaning if you were expecting to just change ip, it won’t work…
I found my solution in mailu documentation, which recommands to use this instead of official docker ipv6 implementation. It simulates ipv4 behavior with ipv6 : docker-NAT.
I confirm it works :).