This change log covers changes to the docker image and does not include changes to the micromamba program.
- In
.gitattributes
fix line endings for*.sh
files to allow building on Windows
- Start FAQ
- update add_micromamba example to include
USER root
before copying files in
- added support for alpine base image
- bump CUDA 12 to 12.0.1
- added base image
ubuntu:kinetic
- added base image
nvidia/cuda:12.0.0-base-ubuntu22.04
- added base image
nvidia/cuda:12.0.0-base-ubuntu20.04
- Automatically perform shell initialization for
conda
andmamba
if they are installed - Drop the base image
debian:buster
anddebian:buster-slim
as they are no longer under offical debian support - Install shell hooks for
micromamba
,conda
, andmamba
even ifMAMBA_SKIP_ACTIVATE=1
- Moved code from
Dockerfile
to separate bash scripts_dockerfile_initialize_user_accounts.sh
and_dockerfile_setup_root_prefix.sh
- Add images based on nvidia/cuda:*-base-ubuntu*
- Build images from all Debian releases that have not yet reached end of life
- Build images from both slim and non-slim Debian images
- Revamp tagging to support multiple base images
- Change the default username from
micromamba
tomambauser
. - Add the environment variable
MAMBA_USER
to store the value of the default username.
- If environmental variable
MAMBA_SKIP_ACTIVATE
is set to1
, then no conda environment will be automatically activated during adocker run ...
command.
- Images are now built on every push to
main
branch or when cronjob sees that conda-forge has a newer version of micromamba that does not yet have a corresponding image on dockerhub - Images will now also be tagged with a the short version of the git SHA hash from this git repository.
- The outputs of
check_version.py
have been modified to make the build scripts better
- Consolidated activation code into
/usr/local/bin/_activate_current_env.sh
- Moved
_entrypoint.sh
and_docker_shell.sh
into/usr/local/bin
- Stop adding
MAMBA_ROOT_PREFIX/bin
inPATH
. - Remove tests that override entrypoint. Users should not expect their conda env to get activated if they interfere with the entrypoint script.
- Remove test of using
RUN
command with 'exec' form to access conda installed software. This required thePATH
modification that is being removed. Use 'shell' form ofRUN
command instead. - Remove call to
micromamba
that adds shell completion commands from.bashrc
, as this is now included in the shell hooks command.
- Activation of conda env during docker build is now triggered by
ARG MAMBA_DOCKERFILE_ACTIVATE=1
- Entrypoint script moved to
/bin/_entrypoint.sh
SHELL
now set to/bin/_dockerfile_shell.sh
, which activates an environment within the docker build ifMAMBA_DOCKERFILE_ACTIVATE=1
and then executes any arguments using/bin/bash
- Move setup of bash environment from entrypoint to .bashrc
- Modifications to .bashrc are done during image build
- Entrypoint evaluates the micromamba shell hook directly
- Entrypoint no longer writes to ~/.bashrc
- base image changed from debian:buster-slim to debian:bullseye-slim
- added tests to check that example Dockerfiles build
- add build for pcc64le
- default user changed from root to micromamba