docs

Wireguard + GUI: https://github.com/wg-easy/wg-easy Managing all those household docs: https://docs.paperless-ngx.com Backups of mail accounts: https://www.offlineimap.org Cloud storage for phones: http://nextcloud.com Mirroring podcasts locally: https://github.com/akhilrex/podgrab Managing dynamic service dns via plugins: https://coredns.io My own matrix instance: https://matrix-org.github.io/dendrite/ Backups: https://restic.net Media Management: https://jellyfin.org Relay only tor help: https://www.torproject.org S3 compatible storage: https://github.com/seaweedfs/seaweedfs Git + CI: https://about.gitlab.com Managing SSL and container proxying: https://traefik.io Mirror the docker registry locally: https://github.com/docker-library/docs/tree/master/registry Samba support for the windows hosts: https://github.com/ServerContainers/samba

There are Alpine [1] and Debian [2] miniconda images (within which you can `conda install python==3.8` and 2.7 and 3.4 in different conda envs) [1] https://github.com/ContinuumIO/docker-images/blob/master/min... [2] https://github.com/ContinuumIO/docker-images/blob/master/min... If you build manylinux wheels with auditwheel [3], they should install without needing compilation for {CentOS, Debian, Ubuntu, and Alpine}; though standard Alpine images have MUSL instead of glibc by default, this [4] may work: echo "manylinux1_compatible = True" > $PYTHON_PATH/_manylinux.py [3] https://github.com/pypa/auditwheel [4] https://github.com/docker-library/docs/issues/904#issuecomme... The miniforge docker images aren't yet [5][6] multi-arch, which means it's not as easy to take advantage of all of the ARM64 / aarch64 packages that conda-forge bui

We tried those flags in the beginning since it was introduced in docker openjdk image[1]. When we dug in further, we find its just not trouble free (i.e. experimental). The default is to use 1/4th of RAM which is entirely inefficient [2]. The "MaxRAMFraction" parameter allows to specify 1/n fraction and not possible to efficiently use 65% or 75% of memory. The only place to start is to set MaxRAMFraction=2 and that already means only 50% of memory is used for heap. That produces a lot of wastage. A lot of resource efficiency is gained by starting with 65% or 80%. OpenJDK 10 is introducing a new option "MaxRAMPercentage" [3] and that goes closer to making a script unnecessary. TL;DR - The default flags are still experimental in JDK 8/9, and deemed to be better on Java 10. A script is just better for consistency. 1: https://github.com/docke

Primary curator of the program here (https://github.com/docker-library/official-images/blob/319cb...). "Moving" is a bit of a strong word. It would be much more accurate to say "providing alternatives". For example, the "golang" image now has an "alpine" variant for each supported version (https://hub.docker.com/_/golang/), but the default variant is still Debian-based (especially given that switching the base outright would break far too many existing Dockerfiles). Additionally, the documentation calls out that there might be libc compatibility issues in the spirit of trying to ensure our users are properly informed about the potential problems they might run into in their quest for the smallest possible base: https://github.com/docker-library/docs/blob/b7b6b86124682ef1... I would definitely welcome PRs to make this verbiage more accu