unable to run multiple instances of earthly with different container names due to port bind issue

[alexcb]

What went wrong?

earthly --buildkit-container-name=foo +base
earthly --buildkit-container-name=bar +base

will cause once instance to die with:

           buildkitd | Starting buildkit daemon as a docker container (foo)...
Error: build new buildkitd client: maybe start buildkitd: start: could not start buildkit: 1 error occurred:
	* command failed: docker run --privileged --env BUILDKIT_TLS_ENABLED=false --env BUILDKIT_MAX_PARALLELISM=20 --env BUILDKIT_DEBUG=false --env BUILDKIT_TCP_TRANSPORT_ENABLED=false --label dev.earthly.settingshash=e9fe7910efadcc66 --mount type=volume,source=earthly-cache,dst=/tmp/earthly --publish 127.0.0.1:8371:8371/tcp -d --pull missing --name foo docker.io/earthly/buildkitd:prerelease: exit status 125: 43c2888e5e326dd00585043393c672b129bb48c0a018dc445ef330bb613bfc1b
docker: Error response from daemon: driver failed programming external connectivity on endpoint foo (f934896c3c83a20737e48c0a2f8ebf359aeb5dc2159cccc552682fd9e3f146d1): Bind for 127.0.0.1:8371 failed: port is already allocated.: exit status 125

What should have happened?

a unique port should be picked automatically

What earthly version?

$ earthly --version
earthly version prerelease e640ac418062c5457500a656d200cf01dfee3284 linux/amd64; Ubuntu 23.10 (Mantic Minotaur)

Buildkit Logs

No response

Other Helpful Information

No response

[vladaionescu]

It's possible to use different instances via installation name. That will also choose a different port.