Replicable build environment for MicroPython
Build the docker image, you can overwrite the default versions by setting the
VERSION_V1 and VERSION_V2 arguments with a MicroPython git tag:
docker build -t "ubit-upy-img" --build-arg VERSION_V1=v1.0.0 --build-arg VERSION_V2=v2.0.0 .
Either of the builds can be skipped by passing the "skip" string to the
version build argument, e.g. --build-arg VERSION_V1=skip
For better traceability it's recommendable to save the build output, so preferably do:
docker build -t "ubit-upy-img" --build-arg VERSION_V1=v1.0.0 --build-arg VERSION_V2=v2.0.0 . 2>&1 | tee docker_build_op.txt
docker run --name ubit-upy-container ubit-upy-img
docker cp ubit-upy-container:/home/artefacts .
docker save ubit-upy-img > ubit-upy-img.tar
gzip -c ubit-upy-img.tar > ubit-upy-img.tar.gz
gzip -d ubit-upy-img.tar.gz
docker load < ubit-upy-img.tar
docker image ls -a
To run a bash session in a new container from an existing Docker image:
docker run -it --entrypoint /bin/bash ubit-upy-img
The contents of this repository are released under the MIT LICENse.
SPDX-License-Identifier: MIT
Trust, partnership, simplicity and passion are our core values we live and breathe in our daily work life and within our projects. Our open-source projects are no exception. We have an active community which spans the globe and we welcome and encourage participation and contributions to our projects by everyone. We work to foster a positive, open, inclusive and supportive environment and trust that our community respects the micro:bit code of conduct. Please see our code of conduct which outlines our expectations for all those that participate in ou community and details on how to report any concerns and what would happen should breaches occur.