Container Manager oder Docker auf IPv6 umstellen

[Silverstation]

Hallo Zusammen,

ich habe aktuell das Problem, dass meine pi-hole bzw mein Proxy nur auf ipv4 läuft und somit mein ipv6 Netzwerk nicht mit schützen kann.
Nur auf IPv4 stellen ist nciht machbar, da ich durch DSLite dazu gezwungen werde.

In meinem Container Manager habe ich wieso auch immer nur ein Host Netzwerk mit automatisch deaktiviertem IPv6

Ich kann das in keiner Weise irgendwie anpassen oder ändern.

Jeder Forumbeitrag der von eingerichteten MACVLANS über json Anpassungen bis hin zu extra Bridge Netzwerke sind bei mir nicht von Erfolg gekrönt.

Ich schließe allerdings mein eigenes menschliches Versagen nicht aus!

Haben wir eventuell Ideen, Gedächtnisstützen oder Erfahrungen dahingehend?

 

[DaveR]

You're going to have to get your hands dirty and edit 3 files via SSH. I prefer editing the files using WinSCP.

Note: The following dockerd.json examples contain "2001:db8:1::/64". Replace "2001:db8:1::/64" with your network's cidr range.

First stop Container Manager.

Then edit /var/packages/ContainerManager/etc/dockerd.json so it contains:

{"data-root":"/var/packages/ContainerManager/var/docker","log-driver":"db","registry-mirrors":[],"storage-driver":"btrfs","ipv6":true,"fixed-cidr-v6":"2001:db8:1::/64"}

Next edit /var/packages/ContainerManager/target/config/dockerd.json so it contains:

{
    "registry-mirrors": [],
    "data-root": "/var/packages/ContainerManager/target/docker",
    "log-driver": "db",
    "ipv6": true,
    "fixed-cidr-v6": "2001:db8:1::/64"
}

When ContainerManager starts it removes the "ipv6":true, from /var/packages/ContainerManager/etc/dockerd.json

To prevent this you need to edit /var/packages/ContainerManager/scripts/start-stop-status by commenting out this line (line 192)
$DockerUpdaterBin postinst updatedockerdconf "$(get_install_volume_type)"

so you have:
#$DockerUpdaterBin postinst updatedockerdconf "$(get_install_volume_type)"

Finally start ContainerManager.

Note: You will need to do this again when the Container Manager package updates to a new version.

I might write a script to do the edits to make it easy for people.

EDIT Replaced a Docker that should have been ContainerManager

EDIT 2 This enables IPv6 for the bridge network.

 

[Silverstation]

Well Sadly i tried and still my Host Network is deactivated on Container Manager. what did i do Wrong?

1. i first stopped Containermanager with
synopkgctl stop ContainerManager

2. I edited /var/packages/ContainerManager/etc/dockerd.json

vi /var/packages/ContainerManager/etc/dockerd.json

exit from VI via ":wq" i also checked if the file was really edited via:
cat /var/packages/ContainerManager/etc/dockerd.json
3. I edited /var/packages/ContainerManager/target/config/dockerd.json
vi /var/packages/ContainerManager/target/config/dockerd.json

4. at last i edited /var/packages/ContainerManager/scripts/start-stop-status
vi /var/packages/ContainerManager/scripts/start-stop-status

After Starting ContainerManager with
synopkgctl start ContainerManager
My Host Network is still like this:



Is there a misunderstanding on my side?

 

[DaveR]

I've released a script that it does it all, including backing up the files it edits.
https://github.com/007revad/Synology_ContainerManager_IPv6

I edited my post just 40 minutes ago to say that it enables IPv6 on the bridge network.

 

[Kachelkaiser]

Great work, thank you!!!

But in your manual the screenshots are missing

 

[DaveR]

But in your manual the screenshots are missing

The images have been added now.

 

[matt42]

@DaveR your script is great and it does the changes it is supposed to do, however it results in the package (either ContainerManager or Docker) being unusable. Both package manager's claim the package to be corrupt and requiring repairs. Only by reverting the changes back out was the package able to start again.