Chris Crowe
5969c76ee1
2022.02.1 ( #101 )
...
Update base container to 2022.02.1
2022-02-13 08:55:58 -08:00
Chris Crowe
5d990c297b
Upgrading base container to 2022.01.1 ( #93 )
2022-01-07 18:53:23 -08:00
Chris Crowe
8cb2c34de4
Upgrading base container to 2021.12 ( #92 )
...
* Upgrading base container to 2021.12
* Bumping to 2021.12.1
2021-12-26 14:09:08 -08:00
Chris Crowe
4769b48e9a
Updating base container to 2021.10.1 ( #81 )
2021-10-26 08:42:54 -07:00
Chris Crowe
5e36fcb3e7
Update pihole base container to 2021.09 ( #76 )
2021-10-06 08:47:49 -07:00
Chris Crowe
3a3e03fd09
Update pihole base container to 2021.09 ( #72 )
...
* Update pihole base container to 2021.09
* README typo fix
2021-09-19 17:20:56 -07:00
Chris Crowe
4d7fac1d67
Updating to new v5.8.1 base container ( #63 )
...
Seems the Pi-Hole team reused the same Docker image tag...
2021-08-10 23:17:04 -07:00
Chris Crowe
ab6bf5c5bc
Update pihole base container to v5.8.1 ( #48 )
2021-04-21 18:44:11 -07:00
Chris Crowe
9a585c9992
Updating base container to v5.8 ( #46 )
2021-04-15 23:46:54 -07:00
Chris
7b41e2bf42
Updating to pihole container v5.6
...
Also lockingt he base container version in the Dockerfile,
I'll be doing releases like this from now on
2021-02-08 23:34:03 -08:00
Chris Crowe
8fd6c18701
Update base image to v5.5.1 ( #17 )
...
* Rename init script
* Bumping base pihole container to v5.5.1
Also renumbering releases to match Pi-Hole releases
2021-01-19 09:04:44 -08:00
Chris Crowe
f976f463db
Single container support ( #11 )
...
Adding a 2nd docker-compose config for running both Pi-Hole and Unbound in the same container (following recommended steps in the Pi-Hole docs).
Restructuring the project to maintain the old 2-container setup as well.
2020-12-31 12:23:33 -08:00
