docker
/
docker-pi-hole
mirror of https://github.com/pi-hole/docker-pi-hole.git
1
0
Fork 0
Code Issues Releases Wiki Activity
docker-pi-hole/TESTING.md

25 lines
900 B
Markdown
Raw Normal View History

Create TESTING.md
2017-10-16 22:38:59 +02:00
# Prerequisites
make prerequisites more precise
2022-02-01 00:17:59 +01:00
Make sure you have bash & docker installed.
Fix formatting, typos and the link Signed-off-by: Sebastian Haderecker <sebastian.haderecker@gmail.com>
2020-12-23 17:21:23 +01:00
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).
Create TESTING.md
2017-10-16 22:38:59 +02:00
# Running tests locally
Introduce additional docker tags for the debian version. * 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>
2020-06-04 23:03:48 +02:00
`ARCH=amd64 ./gh-actions-test.sh`
Create TESTING.md
2017-10-16 22:38:59 +02:00
Fix formatting, typos and the link Signed-off-by: Sebastian Haderecker <sebastian.haderecker@gmail.com>
2020-12-23 17:21:23 +01:00
Should result in:
Create TESTING.md
2017-10-16 22:38:59 +02:00
Fix formatting, typos and the link Signed-off-by: Sebastian Haderecker <sebastian.haderecker@gmail.com>
2020-12-23 17:21:23 +01:00
- An image named `pihole:amd64` being built
- Tests being ran to confirm the image doesn't have any regressions
Create TESTING.md
2017-10-16 22:38:59 +02:00
update testing readme for tox
2017-10-17 07:21:43 +02:00
# Local image names
Beta v5.0 Signed-off-by: Adam Hill <adam@diginc.us>
2020-02-04 06:39:03 +01:00
Docker images built by `Dockerfile.py` are named the same but stripped of the `pihole/` docker repository namespace.
update testing readme for tox
2017-10-17 07:21:43 +02:00
Update way too much - Tox py3.7 + pipenv - Python3 Dockerfile.py - Dockerfile.py tags remote instead of just local image names now - Circle.sh instead of in-line circle.yml script breakout - probably other stuff I forgot - Docker images build during the tests should hopefullly now be available at the deploy job workflow thanks to shared docker layers. - Rename aarch64 to arm64 to reduce custom map
2020-01-14 15:37:44 +01:00
e.g. `pi-hole:debian_amd64` or `pi-hole-multiarch:debian_arm64`
update testing readme for tox
2017-10-17 07:21:43 +02:00
Fix formatting, typos and the link Signed-off-by: Sebastian Haderecker <sebastian.haderecker@gmail.com>
2020-12-23 17:21:23 +01:00
You can run the multiarch images on an amd64 development system if you [enable binfmt-support as described in the multiarch image docs](https://hub.docker.com/r/multiarch/debian-debootstrap/)
update testing readme for tox
2017-10-17 07:21:43 +02:00
`docker run --rm --privileged multiarch/qemu-user-static:register --reset`