@jackhftang FWIW, I personally started using @moigagoo's image because it is mentioned in the Nim docs: <https://nim-lang.org/install_unix.html>. It is, however, labeled as "Community managed".
@moigagoo This repository seems to contain the info on how to create and maintain official images: <https://github.com/docker-library/official-images>. This section in docker documentation also provides a tl;dr: <https://docs.docker.com/docker-hub/official_images/#creating-a-docker-official-image>. It looks like the docker-library project then handles the CI part? Interestingly, Python's official image seems to be generated from <https://github.com/docker-library/python>, whereas Rust's appears to be generated from <https://github.com/rust-lang/docker-rust>. Maybe @Araq or somebody else can chime in on which approach (image repo in `docker-library` or `nim-lang` organization) would be preferable for Nim? In any case, official images seem to be maintained collaboratively with the docker-library maintainers. As to _why_ we'd maybe want to have an official image: * Having the green official badge on an image can be important when somebody is looking for a production-grade image (security and otherwise) * People may be more likely to discover an image when its official. For example, AWS seems to mirror docker official images in the ECR public gallery: <https://aws.amazon.com/blogs/containers/docker-official-images-now-available-on-amazon-elastic-container-registry-public/>
