Closed truppelito closed 1 year ago
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Did you ever figure out a fix for this? I'm also not able to get ipv6 updates working. Using the ipv6=yes
option also results in an error message:
WARNING: file /ddclient.conf, line 23: Invalid Value for keyword 'ipv6' = 'yes'
It's as if ipv6 support is completely missing.
No, unfortunately. I eventually found another way to update dynv6.com without using ddclient.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
did you guys configure ipv6 in your custom bridge? docker doesn't just magically work with ipv6... is there a valid ipv6 address inside your container?
A human has marked this issue as invalid, this likely happened because the issue template was not used in the creation of the issue.
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.
no response, closing.
This issue is locked due to inactivity
Expected Behavior
I'm running this image on a raspberry pi with the following config file:
I expected ddclient to update the IPv6 address. In fact, by installing ddclient directly with
sudo apt-get install ddclient
and running it withsudo ddclient -file /path-to-config-file/ddclient.conf
I get this expected behaviour.Current Behavior
By executing
ddclient -file /config/ddclient.conf
in the container I get the following output:Steps to Reproduce
Explained above.
Environment
OS: Linux raspberrypi 5.15.61-v8+ CPU architecture: arm64 How docker service was installed: Using apt-get
Command used to create docker container (run/create/compose/screenshot)
Docker logs
A very large number of copies of this line:
WARNING: file /ddclient.conf, line 3: unrecognized keyword 'usev6' (ignored)