do: use GOLANG_VERSION arg #113
Conversation
pass the arg, and use it in the iidfile cache filename so that using a different value doesn't keep using the same cached image id.
| docker run \ | ||
| --tty --interactive --rm \ | ||
| -v "$PWD:/work" \ | ||
| -v ~/.cache/go-build:/root/.cache/go-build \ | ||
| -v ~/go/pkg/mod:/go/pkg/mod \ | ||
| -w /work \ | ||
| "$tag" bash | ||
| "$image" \ | ||
| "${@-bash}" |
There was a problem hiding this comment.
Wondering if DOCKER_BUILDKIT=1 is an option, in that case, you could use the docker build --output=.. option to get artifacts out of the build, instead of first building, then running the image
There was a problem hiding this comment.
Oh interesting!
In this case I don't think there will necessarily be any output. The goal is to run an interactive shell and potentially run multiple commands in it.
If someone wants to try something against a different Go version it is a convenient way of getting a container running with that version.
There was a problem hiding this comment.
Ah, gotcha; didn't look closely at all use-cases, but the --output option is very interested for "building" artefacts (and can make things a lot more simple). Only issue would be if you want to do so with native Windows containers (windows doesn't yet support buildkit)
pass the arg, and use it in the iidfile cache filename so that using a different value doesn't keep using the same cached image id.