commercialhaskell / commercialhaskell/stackage

Corralling the proliferation of container images

Open
#7,397 4 comments 1 reaction 0 assignees View on GitHub
type: enhancement
Dominant language
Dockerfile
Stars
551
Forks
825
Avg merge
2d 16m
Merged PRs (30d)
8

Description

I've got a question about container images.

`automated/build.sh` runs most of its actions in an image [ghcr.io/commercialhaskell/stackage/build](http://ghcr.io/commercialhaskell/stackage/build) . This image is built in a GitHub Action on the stackage repo. Its source is Dockerfile at the root of the stackage repo.

Separately, an image https://hub.docker.com/r/fpco/stack-build is built from within `automated/build.sh` itself. It's built from automated/dockerfiles/lts-*/Dockerfile .

Both images are tagged for particular LTSs, and both include all the system packages needed for building all of Stackage. The Dockerfiles RUN the same underlying scripts docker/*.sh .

I guess my first question is why are there two separate processes for creating similar-but-different images?

Second question - perhaps automated/dockerfiles/lts-22.7/Dockerfile should be setting the same STACK_VERSION as Dockerfile?

Third question: should we deprecate the Dockerhub images?

*sorry for the issue title*

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.