Portainer - pi hole container upgrade

Currently reading
Portainer - pi hole container upgrade

752
256
NAS
DS1815+, DS1819+, DS1522+
Operating system
  1. Windows
Mobile operating system
  1. iOS
Afternoon all - posted this in the community, thought I'd try here for additional input/response:

I followed a tutorial last fall that creates a pi hole server (container) within Portainer. At the end of the tutorial, it indicates that the pihole server is upgradable by shutting in the container down and recreating the pi hole container. It did recreate, but multiple restart attempts indicated the container was unhealthy with a message of health check, but I don't have enough experience with docker to understand what broke, or attempt a fix. I ended up having to remove portainer, remove docker, and recreate it from scratch to get it up and running. Any insight/advice is appreciated.
 
Last edited:
It did recreate, but multiple restart attempts indicated the container was unhealthy
Can you share which image you used and in case you used a docker-compose.yml the link to the compose.yml?

I am currious to check wether the Dockerfile and/or compose.yml declare healtchecks.

Most healthchecks are quiet primitive and perform a command inside the container that tries to identify whether the main process is responding. By default the interval for healthchecks is 30 seconds, starting it's first check after the container is started and the intervall is passed. E.g. the first check happens 30 seconds after container starts and then repeats every 30 seconds.

Afair, appart from informing the user that a container is "unhealthy" it should have NONE consequences. Though, if you run the same container in swarm mode (which is broken on Syno's Docker), the swarm internal loadbalancer will start forwaring traffic to the target container once its flagged healthy. Though, outside swarm, I am uncertain if it provides more than a cosmetic detail.

.. and then there is the possibility, that the healthcheck itself has an error :)
-- post merged: --

The image pihole/pihole declares following healthcheck:
dig +norecurse +retry=0 @127.0.0.1 pi.hole || exit 1
This healthcheck uses dig to resolve the name pi.hole using the dns service provided by pihole (accessed by the localhost ip127.0.0.1). If the name resolution fails, the health check fails.

I assume pi.hole is a default entry, which should always be resolvable. If you managed to delete that entry or prevent it beeing created somehow, the health check will start failing.
 
Thank you for input/feedback. I think I saw something in the log file about DNS - I will post the link when I get home to the tutorial I followed that details the setup and upgrade process for the portainer docker container.
 

Create an account or login to comment

You must be a member in order to leave a comment

Create account

Create an account on our community. It's easy!

Log in

Already have an account? Log in here.

Similar threads

How did you create the Portainer container in first place? As in exact docker run commands or in case...
Replies
7
Views
1,667
Looks like I triggered you somehow with my post: it was not my intention. I have no idea whether bash or...
Replies
4
Views
2,052
Another aspect that might indicate it is that the swarm mode finally works! It is the first Synology...
Replies
4
Views
955
Replies
3
Views
1,005
I can’t find any option to restore just the settings. 1710356648 Phew, managed to fix it. Within the...
Replies
4
Views
736
  • Question
Open an issue on that GitHub page. The developers will be glad to assist. OP has posted two threads on...
Replies
5
Views
1,387
I'm happy with email notifications but in v0.3.3 of dockcheck the author added apprise notifications...
Replies
4
Views
1,670

Welcome to SynoForum.com!

SynoForum.com is an unofficial Synology forum for NAS owners and enthusiasts.

Registration is free, easy and fast!

Trending threads

Back
Top