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

provisioning on hetzner with no IPV4 fails #13

Open
6543 opened this issue Aug 17, 2023 · 3 comments
Open

provisioning on hetzner with no IPV4 fails #13

6543 opened this issue Aug 17, 2023 · 3 comments
Labels
enhancement Enhance existing feature

Comments

@6543
Copy link
Member

6543 commented Aug 17, 2023

if WOODPECKER_HETZNERCLOUD_PUBLIC_IPV4_ENABLE=false is set, no agent task is provisioned on the host

@xoxys
Copy link
Member

xoxys commented Aug 17, 2023

I guess that's related to not working dual-stack setup for the docker engine (assuming the server can be reached via Ipv6).

@6543
Copy link
Member Author

6543 commented Aug 17, 2023

the idea behind: ipv4 cost us ipv6 don't :)

@xoxys
Copy link
Member

xoxys commented Aug 17, 2023

Makes sense, in addition to the docker engine as mentioned above, the networks dynamically created by Woodpecker for each workflow need to be IPv6 enabled as well.

[
    {
        "Name": "wp_01h81t1q0hhd2m6r1hh3jkghk5_0_default",
        "Id": "800649be2df9e9039b6603271e9c3f840712a0324925d988aacbe7c7eb89bc01",
        "Created": "2023-08-17T13:14:58.086048729Z",
        "Scope": "local",
        "Driver": "bridge",
        "EnableIPv6": false,

@xoxys xoxys added the enhancement Enhance existing feature label Mar 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Enhance existing feature
Projects
None yet
Development

No branches or pull requests

2 participants