alpha
/
Kaleidoscope
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'f14e991e58'
${ noResults }
Kaleidoscope/bin/run-docker

41 lines
1.6 KiB
Raw Normal View History Unescape

Add a small tool, to run things within Docker To make it easier to reproduce things, and to help build in a clean environment, this adds a thin Dockerfile that has Arduino and arduino-cli pre-installed, and - along with the `bin/run-docker` script - is set up so that one can easily run arbitrary commands in the context of the current bundle and Kaleidoscope. The first run will take a while, because docker will build the image. Subsequent runs will use the cache. To use: `bin/run-docker make`, for example. Any argument passed to the `bin/run-docker` will be eval-ed within the container, and will run there. Signed-off-by: Gergely Nagy <algernon@keyboard.io>
4 years ago
#! /bin/sh
## -*- mode: sh -*-
set -e
uname_S=$(uname -s 2>/dev/null || echo not)
if [ "${uname_S}" = "Darwin" ]; then
ARDUINO_LOCAL_LIB_PATH="${ARDUINO_LOCAL_LIB_PATH:-${HOME}/Documents/Arduino}"
Rework our Docker config for performance * never try to write anything to the host's disks * read as little as possible from the host's disks * keep source in ram * cache build artifacts and intermediate content persistently Most of these hacks are only necessary because Docker disk performance on macOS is...not performant Signed-off-by: Jesse Vincent <jesse@keyboard.io> Signed-off-by: Gergely Nagy <algernon@keyboard.io>
4 years ago
# This stops macos from copying resource forks into thigns like tar
export COPYFILE_DISABLE=true
Set BOARD_HARDWARE_PATH correctly for run-docker on macOS Because ARDUINO_LOCAL_LIB_PATH was being set to a default value for other operating systems before checking the OS version, it would never get set correctly for macOS (unless it was already set externally). This change fixes that problem so that it's no longer necessary to set BOARD_HARDWARE_PATH externally when executing `run-docker`. Signed-off-by: Michael Richters <gedankenexperimenter@gmail.com>
4 years ago
else
ARDUINO_LOCAL_LIB_PATH="${ARDUINO_LOCAL_LIB_PATH:-${HOME}/Arduino}"
Add a small tool, to run things within Docker To make it easier to reproduce things, and to help build in a clean environment, this adds a thin Dockerfile that has Arduino and arduino-cli pre-installed, and - along with the `bin/run-docker` script - is set up so that one can easily run arbitrary commands in the context of the current bundle and Kaleidoscope. The first run will take a while, because docker will build the image. Subsequent runs will use the cache. To use: `bin/run-docker make`, for example. Any argument passed to the `bin/run-docker` will be eval-ed within the container, and will run there. Signed-off-by: Gergely Nagy <algernon@keyboard.io>
4 years ago
fi
BOARD_HARDWARE_PATH="${BOARD_HARDWARE_PATH:-${ARDUINO_LOCAL_LIB_PATH}/hardware}"
Rework our Docker config for performance * never try to write anything to the host's disks * read as little as possible from the host's disks * keep source in ram * cache build artifacts and intermediate content persistently Most of these hacks are only necessary because Docker disk performance on macOS is...not performant Signed-off-by: Jesse Vincent <jesse@keyboard.io> Signed-off-by: Gergely Nagy <algernon@keyboard.io>
4 years ago
echo "Preparing Kaleidoscope and the bundle..."
XFER_DIR="$(pwd)/.docker_xfer"
mkdir -p "${XFER_DIR}"
tar -cf "${XFER_DIR}/kaleidoscope.tar" \
--exclude .docker_xfer --exclude .git --exclude _build --exclude testing/googletest/build \
.
(cd "${BOARD_HARDWARE_PATH}/keyboardio" && tar -cf "${XFER_DIR}/bundle.tar" \
--exclude .git --exclude avr/libraries/Kaleidoscope .)
echo "Building the docker image..."
docker build -q -t kaleidoscope/docker etc
Add a small tool, to run things within Docker To make it easier to reproduce things, and to help build in a clean environment, this adds a thin Dockerfile that has Arduino and arduino-cli pre-installed, and - along with the `bin/run-docker` script - is set up so that one can easily run arbitrary commands in the context of the current bundle and Kaleidoscope. The first run will take a while, because docker will build the image. Subsequent runs will use the cache. To use: `bin/run-docker make`, for example. Any argument passed to the `bin/run-docker` will be eval-ed within the container, and will run there. Signed-off-by: Gergely Nagy <algernon@keyboard.io>
4 years ago
docker run --rm -it \
Rework our Docker config for performance * never try to write anything to the host's disks * read as little as possible from the host's disks * keep source in ram * cache build artifacts and intermediate content persistently Most of these hacks are only necessary because Docker disk performance on macOS is...not performant Signed-off-by: Jesse Vincent <jesse@keyboard.io> Signed-off-by: Gergely Nagy <algernon@keyboard.io>
4 years ago
--tmpfs /kaleidoscope:exec \
--mount type=bind,source="${XFER_DIR}",destination=/kaleidoscope-src,consistency=delegated,readonly \
--mount type=volume,source=kaleidoscope-persist,destination=/kaleidoscope-persist,consistency=delegated \
--mount type=volume,source=kaleidoscope-googletest-build,destination=/kaleidoscope/hardware/keyboardio/avr/libraries/Kaleidoscope/testing/googletest/build,consistency=delegated \
--mount type=volume,source=kaleidoscope-build,destination=/kaleidoscope/hardware/keyboardio/avr/libraries/Kaleidoscope/_build,consistency=delegated \
kaleidoscope/docker "$*"
exit 0