Why not in both?

Is git really needed in the head image? If so, I'll happily add it.
BTW, what is head actually used for?

I don't even know what the release image is really used for, but I imagine similar things for both.

I'm trying to use the release image (built by Dockerfile.release and pushed to crystallang/crystal:0.x.x) on our GitLab CI. I think that's a common use-case. Here, git is useful to use shards.

I suppose that the head images (built by Dockerfile) is used to build crystal itself??
If so, you don't need git there.

Just guessing... 8-)

The official release packages are built from crystal-lang/omnibus-crystal. Travis CI support uses the debian packages built by omnibus, as well as the nightly packages built by my fork of the omnibus project. Crystals own Travis CI setup uses the images from jhass/crystal-build-docker.

@jhass Thank you for the explanations!

Last question, how are images on docker.io built?
https://hub.docker.com/r/crystallang/crystal/~/dockerfile/ states a Dockerfile which includes llvm.

Running crystallang/crystal:0.17.2 show that it does not contain llvm:

$ docker run -it crystallang/crystal:0.17.2 ls /opt
crystal

Running crystallang/crystal:head DOES contain llvm:

$ docker run -it crystallang/crystal:head ls /opt
crystal  crystal-head  llvm-3.5.0-1

My conclusion, Dockerfile builds head. Dockerfile.release build release images 0.x.x.

I hope I'm right %-)

@splattael That's exactly right. I think head is built automatically. We manually use Dockerfile.release to create images after each release. But I don't know much about all this, I just run some scripts @waj gave me 😊 (he used to do that, but since I do the part related to omnibus it's better if I do it too so we don't forget to do it). I guess it's OK for git to be in both images because you'll likely want to use shards.

@jhass @asterite Ok, got it!

I've added git to Dockerfile.release, so git is now available in head and 0.x.x docker images 💃

PR is rebased.

Thanks!

💚