Portainer recreate pihole container with latest version not possible

Help
1

Hello,

I wanted to update my pihole, but at the moment I get errors via portainer webgui.
In the past, there was no problem.

I get this error, when I recreate the container.

image
image351×148 6.65 KB

The yellow lighted image should be used, I don't know how I can fix the problem.

image
image2238×390 41.1 KB

2

Portainer recreate pihole container with latest version not possible

This is not true.

I'm running 2 containers. Both were started using Portainer.

Error 500 in Portainer only means the container creation failed, but we need more information about the error.

  • Did you create a completely new container or did you try to "Duplicate/Edit" the previous container?
  • Did you read the v6 README file? Did you applied the necessary changes to use the new environment variables?
  • Can you show the container options you are using?
3

When I want to add the recommended variables, I can only deploy the container as new, and then I get this error. ( I wanted to duplicate / edit)

image
image241×234 10.4 KB

4

You are trying to run a new image using the old (v5) settings.

There is no /s6-init in the new image.

Set the entrypoint as "Default":

image
image432×255 11.7 KB

5

Thank you very much. Now it works :slight_smile:

6

I have also troubles edit/duplicate with portainer and end up with Error500.
I added the last 3 variables and also the Entrypoint as explained above.
Yes, I am not that experienced, but maybe some path are wrong?

PiHoleEnv
PiHoleEnv1310×749 73.8 KB

The Volumes maybe?

PiHoleVolumes
PiHoleVolumes889×323 24.5 KB

Thanks a lot.

7

The Portainer error 500 is not very useful. There are no details to understand what is wrong, but I can suggest a few changes:

  1. You are using the wrong variables:

    I marked in red the invalid variables. I also marked in yellow the unnecessary ones (you can remove them):

    image
    image1310×749 70.8 KB

    Only the last 3 are valid and needed.

  2. volumes:

    The volumes are correct, but if you don't use custom dnsmasq files (this is an advanced option), you can remove the /etc/dnsmasq.d volume.

  3. Recreating the container:

    Portainer warns these issues are expected when you change the image:

    image
    image987×158 10.7 KB

    My suggestion is to completely destroy the old container and start a new one using the same volumes and new the variables.

8

Thank you very much for your help :slight_smile: