Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEAT] <Add support for IPV6> #75

Closed
1 task done
d-dandrew opened this issue Oct 10, 2023 · 5 comments
Closed
1 task done

[FEAT] <Add support for IPV6> #75

d-dandrew opened this issue Oct 10, 2023 · 5 comments

Comments

@d-dandrew
Copy link

Is this a new feature request?

  • I have searched the existing issues

Wanted change

Cant start the docker-ddclient with the default docker-compose script
Its confirmed that docker daemon has enabled IPV6 support
docker network inspect ddclient_default shows “EnableIPv6”: false which means ddclient cant access to IPV6 network

Reason for change

ddclient can get ipv6 address on bare metal machine but cant access to ipv6 with lsio image

Proposed code change

No response

@github-actions
Copy link

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

@Roxedus
Copy link
Member

Roxedus commented Oct 10, 2023

first step is to ensure the container has a ipv6 address

@drizuid
Copy link
Member

drizuid commented Oct 10, 2023

Its confirmed that docker daemon has enabled IPV6 support

Its confirmed that docker daemon has enabled IPV6 support` that applies only to the default bridge

docker network inspect ddclient_default shows “EnableIPv6”: false which means ddclient cant access to IPV6 network

which means the custom bridge you have ddclient in is not ipv6 enabled.
this is not something we can fix for you. create your custom bridge with ipv6 enabled

@LinuxServer-CI
Copy link
Contributor

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.

@LinuxServer-CI LinuxServer-CI closed this as not planned Won't fix, can't repro, duplicate, stale Jan 10, 2024
@LinuxServer-CI LinuxServer-CI moved this from Issues to Done in Issue & PR Tracker Jan 10, 2024
Copy link

github-actions bot commented Feb 9, 2024

This issue is locked due to inactivity

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 9, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
Archived in project
Development

No branches or pull requests

4 participants