Replies: 2 comments 1 reply
-
Edit: this issue may have been caused by a bug (#6767) which we've now fixed. Please try deploying it again with the latest image! Original reply: Hi @diedder. Did you run it using plain docker (e.g. a "Container" in portainer) or docker compose (a "Stack" in portainer)? I would recommend using docker compose, using the config defined in our docs https://docs.budibase.com/docs/docker#method-2---docker-compose. Running it manually as a container works as well of course, but it's just a lot more error prone as you have to manually ensure the env variables, volumes and ports etc are set up correctly. Copy and paste that as a portainer stack, change the secrets to something secure and random and then deploy it. I've just ran through that exact procedure and can confirm everything works perfectly. |
Beta Was this translation helpful? Give feedback.
-
@aptkingston
When you pass the redis password as an environment variable, the error is solved and the container is healthy:
|
Beta Was this translation helpful? Give feedback.
-
I've made a new installation wirh the single container install. Everthything seems to work but docker (and portainer ui) marks the container as "unhealthy"
Failurecount raises slowly. How can I fix this? What information to share here for possible investigations?
Beta Was this translation helpful? Give feedback.
All reactions