docker-base-images
docker-base-images copied to clipboard
ocurrent
Generate various Docker ocaml images
It seems there is some duplication between `.opam/repo/default/packages` and `opam-repository/packages`. Is it accidental or on purpose? ```sh >docker run --rm -it ocaml/opam:debian-ocaml-4.13 sh -c 'diff -Naqr .opam/repo/default/packages opam-repository/packages && du...
The base images at the moment build the tips of branches from ocaml/opam which aren't always release tags. This is _brilliant_ during an opam dev cycle, but a little surprising...
I am trying to build arm64 docker images with Docker Desktop on macOS and seeing some packages fail to download during installation. ``` $ echo "FROM ocaml/opam:ubuntu-20.10-ocaml-4.12\nRUN opam install astring"...
We really ought to track the changesets of ocaml/opam when building the opam binary. For example merging this https://github.com/ocaml/opam/pull/4648 should have triggered off a rebuild without requiring manual intervention. (this...
As noted in https://github.com/ocurrent/docker-base-images/issues/98#issuecomment-807862390, the switches created in the base images have `~/opam-repository` as the default remote, so `opam update` does nothing, which is a bit surprising for new users...
At the moment, we copy in the cluster worker's clone of opam-repository, which includes all branches and PRs. We should instead just clone the `master` branch directly within the Dockerfile.
