Error after updating to latest Netbox Image #503
Replies: 2 comments 2 replies
-
I reverted back to using the previous netbox image with this id (sha256:f2df81a43b0aa916d9e39a1c0bc489f2aceb46524f8466d5b0c997d67ec1bcdf) and I was able to successfully start my netbox stack again. I'd still like to keep my netbox images up to date, so if anyone can suggest why the latest netbox image failed that would be great. |
Beta Was this translation helpful? Give feedback.
-
I'm still having this issue and cannot update netbox for docker to version 2.12. I've tried to follow this upgrade guide https://github.com/netbox-community/netbox-docker/wiki/Updating but it seemed to just make things worse. I'm running this stack inside portainer if that's any help, here are the details. docker-compose.yml`version: '3.4' networks: services: postgrespostgres: redisredis: volumes: |
Beta Was this translation helpful? Give feedback.
-
Hi Guys
I use Watchtower to simply tell me when there is a new image to update. Watchtower reported the following
Found new netboxcommunity/netbox:latest image (5c7d396d7af5)
So I pulled the new image and recreated my stack, now I'm getting the following when starting up the netboxdocker_netbox_1
The netboxdocker_postgres_1 container is saying this in the logs.
Can some one help me get this working, at the moment my Netbox is not running and I just get a 502 Bag gateway error when trying to get to it.
Beta Was this translation helpful? Give feedback.
All reactions