mirror of
https://github.com/007revad/Synology_ContainerManager_IPv6.git
synced 2026-04-25 12:15:49 +03:00
[GH-ISSUE #3] Script does not work #1
Labels
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Synology_ContainerManager_IPv6#1
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ianlockhead on GitHub (Jul 9, 2024).
Original GitHub issue: https://github.com/007revad/Synology_ContainerManager_IPv6/issues/3
Hi, the script does not work for me. After running the script Synology can't boot the DSM package and Container Manager needs to be repaired. Fixed cidr was unchanged while I am using the fe80::1/64 as well. Thanks for help
@007revad commented on GitHub (Jul 9, 2024):
What do the following 2 commands return?
@ianlockhead commented on GitHub (Jul 10, 2024):
ianlockhead@Synology:/$ sudo jq . "/var/packages/ContainerManager/etc/dockerd.json"
{
"data-root": "/var/packages/ContainerManager/var/docker",
"log-driver": "db",
"registry-mirrors": [],
"seccomp-profile": "unconfined",
"storage-driver": "btrfs"
}
ianlockhead@Synology:/$ sudo jq . "/var/packages/ContainerManager/target/config/dockerd.json"
{
"registry-mirrors": [],
"data-root": "/var/packages/ContainerManager/var/docker",
"log-driver": "db",
"seccomp-profile": "unconfined"
@007revad commented on GitHub (Jul 10, 2024):
Was that after clicking on Repair in storage manager?
What do these commands return?
@ianlockhead commented on GitHub (Jul 10, 2024):
Hi, yes both json files were restored manually from backup after repairing the syno package.
I can run the script again and paste the cat command output but it will brick the package again I think.
After backup restore the jsons looks:
ianlockhead@Synology:/$ sudo cat "/var/packages/ContainerManager/etc/dockerd.json" && echo
Password:
{"data-root":"/var/packages/ContainerManager/var/docker","log-driver":"db","registry-mirrors":[],"seccomp-profile":"unconfined","storage-driver":"btrfs"}
ianlockhead@Synology:/$ sudo cat "/var/packages/ContainerManager/target/config/dockerd.json" && echo
{
"registry-mirrors": [],
"data-root": "/var/packages/ContainerManager/var/docker",
"log-driver": "db",
"seccomp-profile": "unconfined"
}
Thanks
@007revad commented on GitHub (Jul 10, 2024):
I've been working on a new, much improved, version of the script that uses jq to add the ipv6 key/value pairs to the json files. This will prevent changing any existing custom settings in the json files.
But at the moment it sometimes results in an empty /var/packages/ContainerManager/target/config/dockerd.json
@007revad commented on GitHub (Jul 11, 2024):
Do you want to try the new v2.0.4
@ianlockhead commented on GitHub (Jul 11, 2024):
@007revad The new script 2.0.4 is working like a charm! B-) I have now IPv6 enabled. Thank you so much!!!
Last question.. did you resolve how to support IPv6 on host network driver?
@007revad commented on GitHub (Jul 11, 2024):
Excellent.
From this https://docs.docker.com/config/daemon/ipv6/ webpage it looks like you can only enable IPv6 on the bridge network, or create a new IPv6 network via docker compose.
kerem referenced this issue2026-03-07 19:08:01 +03:00