Image issues - Please Support about container-healthchecks HOT 17 CLOSED

Sorry I think my PR broke this.
I think you need to add the CONTAINER_PRUNE_INTERVAL environment variable for the image to work.

@galexrt Should we add this env to the dockerfile to provide a default value if not explicitly provided?

from container-healthchecks.

@galexrt Yes, I will create a PR

from container-healthchecks.

Ah as written you need to remove the HC_ from the environment variables. That should get it working again.

from container-healthchecks.

@Rustymage Post your docker-compose.yaml or docker run command.

from container-healthchecks.

docker run -d --name bitwarden -v /bw-data/:/data/ -p 76:80 -e SIGNUPS_ALLOWED=false -e ADMIN_TOKEN=TOKEN SMTP_HOST=smtp.gmail.com -e [email protected] -e SMTP_PORT=587 -e SMTP_SSL=true -e [email protected] -e SMTP_PASSWORD=PASSWORD bitwardenrs/server:latest

I use Portainer for management of containers, so I ran the above a few images ago. For this image (broken) and the last several images (working) I download the image and subsequently use the duplicate feature of Portainer to update using the same mount volume to keep the data.

It was only on the image mentioned in the first post that this problem occured.

from container-healthchecks.

I'll check & report back, thanks!

from container-healthchecks.

@swoga Let's add it to the entrypoint.sh to in the future have all custom env var defaults there.

Are you going to create a PR?

from container-healthchecks.

I have finally gotten the time to push a new tag, it should be built soon and available under: v1.16.0-20201006-124530-630.

Edit: v1.16.0-20201006-124530-630 is the right one.

from container-healthchecks.

Hi,

I have used this container and it now won't let me login.

How can I assist to demonstrate whta might have gone wrong?

Thanks.

from container-healthchecks.

@Rustymage You need to register / create an user for that you either need to have working SMTP configured or using the manage.py to create a superuser, e.g., https://github.com/galexrt/docker-healthchecks#create-healthchecks-superuser.

from container-healthchecks.

I already have a working configuration and was upgrading so I wouldn't expect to start fresh or create a new user.

Have I misunderstood?

from container-healthchecks.

@Rustymage What database are you using? If you are using sqlite, have you used a volume?

E.g., have you specified -v ...:... flag

from container-healthchecks.

I have used the default sqlite. I have 1 volume:

/data

I have restored the old image and I can log back in so the data is not lost.

from container-healthchecks.

What is your docker run command and / or environment variables? (Redact secrets from them).

If you have used a very very old image version, the env vars are not prefixe with HC_ anymore, see https://github.com/galexrt/docker-healthchecks#running-the-image for an example docker run command.

from container-healthchecks.

I'm afraid to say I don't have my run command as I've not saved it. I use Portainer to manage.

Here's the env variables.

from container-healthchecks.

Thanks!

from container-healthchecks.

Just wanted to follow up @galexrt and say thanks for the help. I got it all working on the latest image with data intact.

from container-healthchecks.