# Enable IPv6 in created networks

**URL:** <https://forum.gitea.com/t/enable-ipv6-in-created-networks/9696>\
**Category:** Actions\
**Created:** [September 8, 2024, 7:41pm UTC](https://forum.gitea.com/t/enable-ipv6-in-created-networks/9696 "2024-09-08T19:41:44Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![deavmi](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.gitea.com/deavmi/32/6243_2.png) [@deavmi](https://forum.gitea.com/u/deavmi)\
**Post date:** [September 8, 2024, 7:41pm UTC](https://forum.gitea.com/t/enable-ipv6-in-created-networks/9696/1 "2024-09-08T19:41:44Z")

</div>

Is there a way to get the containers that Act runner spawns to use IPv6?

Currently it creates networks with `enable_ipv6` set to `false` and does not take from the default configured address pools.

I am **potentially** willing to pay _some_ money for such a basic feature to be implemented.

---

<div class="post-metadata">

**Author:** ![Matthias](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.gitea.com/matthias/32/6275_2.png) [@Matthias](https://forum.gitea.com/u/Matthias)\
**Post date:** [September 21, 2024, 9:57am UTC](https://forum.gitea.com/t/enable-ipv6-in-created-networks/9696/2 "2024-09-21T09:57:05Z")

</div>

TLDR; As a workaround set the network to which the container attaches to to a fixed ipv6 enabled network (I just used ‘bridge’).  
See [act\_runner/config.example.yaml at main - act\_runner - Gitea: Git with a cup of tea](https://gitea.com/gitea/act_runner/src/branch/main/internal/pkg/config/config.example.yaml#L67)

In more wors:  
I am running a gitea instance on my local network which generally operates on IPv6. When the act\_runner spawns the container, it creates a temporary docker network configured with `"EnableIPv6": true`…  
Clearly this somewhat breaks with my setup.

Because I am on my home network, there is no worry about isolation. Hence, I just configure the runner to use the standard docker bridge network ([act\_runner/config.example.yaml at main - act\_runner - Gitea: Git with a cup of tea](https://gitea.com/gitea/act_runner/src/branch/main/internal/pkg/config/config.example.yaml#L67)).  
This network is configured to enable IPv6, so no problem.

Generally however, I agree with the original post, that customizing the network configuration of the temporary networks is desirable.

---

<div class="post-metadata">

**Author:** ![deavmi](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.gitea.com/deavmi/32/6243_2.png) [@deavmi](https://forum.gitea.com/u/deavmi)\
**Post date:** [September 21, 2024, 10:57am UTC](https://forum.gitea.com/t/enable-ipv6-in-created-networks/9696/3 "2024-09-21T10:57:57Z")

</div>

Hi, perfect.

I eventually figured it out and ended up using the Docker bridge network as I had the configured for IPv6 already.

Perfect!