Alex Couture-Beil comments

Results 256 comments of


                                            Alex Couture-Beil

`WITH DOCKER` is not correctly releasing network resources (and most likely, the network resource is not isolated to a container)

**work-around: clean up after yourself** ``` test: FROM earthly/dind:ubuntu-23.04-docker-24.0.5-1 ARG CACHE_BUSTER RUN echo "running test $CACHE_BUSTER" WITH DOCKER --load myclient:latest=+client RUN \ docker network create --subnet 192.168.200.0/24 foo && \...

`WITH DOCKER` is not correctly releasing network resources (and most likely, the network resource is not isolated to a container)

I expanded my test to have a simple python-based udp server/client which would send messages in a loop, and was able to start two instances in parallel, both of which...

`WITH DOCKER` is not correctly releasing network resources (and most likely, the network resource is not isolated to a container)

Here's another reproduction case: ``` VERSION 0.7 test: FROM docker:dind COPY test-inside-earthly.sh . RUN --no-cache --privileged dockerd-entrypoint.sh & ./test-inside-earthly.sh ``` and ``` #!/bin/sh set -e while ! [ -S /var/run/docker.sock...

`WITH DOCKER` is not correctly releasing network resources (and most likely, the network resource is not isolated to a container)

This issue does not occur when using the `--internal` network option, which "[restricts] external access to the network". Here's a full example: ``` VERSION 0.7 test: FROM earthly/dind:alpine ARG CACHE_BUSTER...

`WITH DOCKER` is not correctly releasing network resources (and most likely, the network resource is not isolated to a container)

Note that the `--internal` work-around posted above, also works with docker-compose networks by using `internal: true`, e.g. ``` networks: frontend: driver: bridge internal: true # example of setting a network...

`WITH DOCKER` is not correctly releasing network resources (and most likely, the network resource is not isolated to a container)

We have documented that `internal` networks should be used whenever possible under https://github.com/earthly/earthly/pull/3515 It's not clear what's needed to support the `external` networks -- **if anyone runs into a specific...