You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After upgrading to release 3.0.0, I've found that Redis Image fails to start with error "Can't handle RDB format version 12".
A recent docker compose pull updated redis:7-alpine to Redis version 7.4.0.
This version is not compatible with the replacement Valkey 8.0.00-rc2 Redis replacement.
Expected Behavior
Valkey 8 does not support the proprietary 7.4.0 Redis database format.
Workaround required or a version that will allow Redis / Valkey to start properly.
Docker Compose Version
Docker Compose version v2.29.2-desktop.2
Docker Version
Client:
Version: 27.2.0
API version: 1.47
Go version: go1.21.13
Git commit: 3ab4256
Built: Tue Aug 27 14:17:17 2024
OS/Arch: windows/amd64
Context: desktop-linux
Server: Docker Desktop 4.34.0 (165256)
Engine:
Version: 27.2.0
API version: 1.47 (minimum version 1.24)
Go version: go1.21.13
Git commit: 3ab5c7d
Built: Tue Aug 27 14:15:15 2024
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.7.20
GitCommit: 8fc6bcff51318944179630522a095cc9dbf9f353
runc:
Version: 1.1.13
GitCommit: v1.1.13-0-g58aa920
docker-init:
Version: 0.19.0
GitCommit: de40ad0
On branch release
Your branch is up to date with 'origin/release'.
Changes not staged for commit:
(use "git add <file>..." to update what will be committed)
(use "git restore <file>..." to discard changes in working directory)
modified: configuration/plugins.py
modified: env/netbox.env
Untracked files:
(use "git add <file>..." to include in what will be committed)
Dockerfile-Plugins
Netbox.yml
plugin_requirements.txt
ssl/
no changes added to commit (use "git add" and/or "git commit -a")
services:
netbox:
image: netbox:latest-pluginsports:
- "8000:8080"# If you want the Nginx unit status page visible from the# outside of the container add the following port mapping:# - "8001:8081"healthcheck:
# Time for which the health check can fail after the container is started.# This depends mostly on the performance of your database. On the first start,# when all tables need to be created the start_period should be higher than on# subsequent starts. For the first start after major version upgrades of NetBox# the start_period might also need to be set higher.# Default value in our docker-compose.yml is 60sstart_period: 120s# environment:# SKIP_SUPERUSER: "false"# SUPERUSER_API_TOKEN: ""# SUPERUSER_EMAIL: ""# SUPERUSER_NAME: ""# SUPERUSER_PASSWORD: ""build:
context: .dockerfile: Dockerfile-Pluginsrestart: unless-stoppednetbox-worker:
image: netbox:latest-pluginsbuild:
context: .dockerfile: Dockerfile-Pluginsrestart: unless-stoppednetbox-housekeeping:
image: netbox:latest-pluginsbuild:
context: .dockerfile: Dockerfile-Pluginsrestart: unless-stoppedpostgres:
restart: unless-stoppedredis:
restart: unless-stoppedredis-cache:
restart: unless-stoppedtls:
image: caddy:2-alpinedepends_on:
- netboxvolumes:
- ./ssl/localhost+2.pem:/etc/ssl/private/localhost.crt:ro,z
- ./ssl/localhost+2-key.pem:/etc/ssl/private/localhost.key:ro,z
- ./ssl/Caddyfile:/etc/caddy/Caddyfile:roports:
- 80:80# Allows for http redirection
- 443:443restart: unless-stopped
The text was updated successfully, but these errors were encountered:
same here... This error message indicates that is attempting to load an RDB file that is in a newer or incompatible format (version 12) that is not supported by the currently running version (7.9.240).
Hi @AnID-BW
The core data is in the Postgres database, so I'm not sure if this is transient data that gets rebuilt from the Postgres data.
Whenever I've moved data between different instances of Netbox, I've only copied a dump of the Postgres database and I've not experienced any issues.
To work around the issue I first did a "docker compose down" and then deleted the netbox-redis-data and netbox-redis-cache-data volumes. These are recreated after the "docker compose up".
I was then able to get Netbox running.
I have a separate issue where I seem to be getting Netbox 4.0.11 instead of 4.1, but I'm unsure if these issues are related. #1305
Current Behavior
After upgrading to release 3.0.0, I've found that Redis Image fails to start with error "Can't handle RDB format version 12".
A recent docker compose pull updated redis:7-alpine to Redis version 7.4.0.
This version is not compatible with the replacement Valkey 8.0.00-rc2 Redis replacement.
Expected Behavior
Valkey 8 does not support the proprietary 7.4.0 Redis database format.
Workaround required or a version that will allow Redis / Valkey to start properly.
Docker Compose Version
Docker Compose version v2.29.2-desktop.2
Docker Version
The git Revision
ab2a7bc
The git Status
Startup Command
docker compose up --detach
NetBox Logs
Content of docker-compose.override.yml
The text was updated successfully, but these errors were encountered: