Ask questions[v2] Distribute binaries for alpine / musl libc
docker run -it --rm docker:latest sh wget "https://d1vvhvl2y92vvt.cloudfront.net/awscli-exe-linux-x86_64.zip" -O "awscliv2.zip" # curl not installed unzip awscliv2.zip ./aws/install # sudo not install
/ # ./aws/install ./aws/install: line 78: /aws/dist/aws2: not found You can now run: /usr/local/bin/aws2 --version / # aws2 sh: aws2: not found
Answer questions bentolor
@blagerweij See the image below from the official Docker image for illustration.
The typical usage is:
docker:dindinstance and then
docker:stableinstance which is linked to the started
dockercommands inside the second container which redirects the comamnds via socket connection to docker daemon running inside the first
Therefore: While it's true that the
docker:dind instance eventually executes your Docker commands, your CLI frontend actually lives in a
docker:stable instance. And that's the place where one i.e. needs to login into AWS ;-)
At least this is the usage pattern I'm aware of (i.e. on using Gitlab CI to build docker images). Maybe there are also direct
docker:dind usage scenarios?