mirror of
https://github.com/pi-hole/docker-pi-hole.git
synced 2024-06-26 00:59:07 +02:00
752d83aeaa
* Added new docker tag variations to specify the debian version ('stretch', and 'buster').
* Arch images are alway as specific as possible: pihole/pihole:master-amd64-stretch
* Multiarch images have both the specific debian version tags as well as the generic non-debian tags: pihole/pihole:master-stretch & pihole/pihole:master
* Currently, the non-specific tags point to the 'stretch' images. Eventaully it can be migrated to 'buster'.
* Use GitHub actions to do the builds. Although the script names include 'gh-actions' to differentiate them from the 'circle' scripts, there is zero logic that is specific to Github (ie. no Github environment variables).
* 'armhf:buster' & 'arm64:buster' has an issue with `ip route get`. I think the issue is related to 'qemu', but I'm not sure. Update the `validate_env` function to only use `ip route get` if `nc` reports something strange.
Signed-off-by: Daniel <daniel@developerdan.com>
897 B
897 B
Prerequisites
Make sure you have bash, docker. Python and some test hacks are crammed into the Dockerfile_build file for now. Revisions in the future may re-enable running python on your host (not just in docker).
Running tests locally
ARCH=amd64 ./gh-actions-test.sh
Should result in :
- An image named
pihole:amd64being build - Tests being ran to confirm the image doesnt have any regressions
Local image names
Docker images built by Dockerfile.py are named the same but stripped of the pihole/ docker repository namespace.
e.g. pi-hole:debian_amd64 or pi-hole-multiarch:debian_arm64
You can run the multiarch images on an amd64 development system if you enable binfmt-support as described in the multiarch image docs
docker run --rm --privileged multiarch/qemu-user-static:register --reset