Open underdarknl opened 5 months ago
Could we spin out the parts of the docker-compose file that handle the extra network into a separate file, and only include it if the env available signals the usability / requirement?
We could do the same for stuff like jeager.
The ipv6 docker-compose addition breaks rollout on services where ipv6 is not available. For example GitPod. Removing this makes the setup run again.
Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error running hook #0: error running hook: exit status 1, stdout: , stderr: failed to add interface veth012dbd4 to sandbox: error setting interface "veth012dbd4" IPv6 to fc42:ca7::2/64: failed to enable ipv6: failed to enable IPv6 forwarding for container's interface eth0: open /proc/sys/net/ipv6/conf/eth0/disable_ipv6: read-only file system: unknown
Originally posted by @underdarknl in https://github.com/minvws/nl-kat-coordination/issues/2256#issuecomment-1907625932