May 22, 20251 yr On 5/19/2025 at 8:33 PM, bmartino1 said:decided to post a compose file as this has been updated and some issues existing in making the docker work due to other settings...Alot of gorups have gon docker compse for easier maintenance...https://github.com/netbox-community/netbox-dockerI recomned using docker compose as there are qute a few side stacks and other worker for netbox to run on unraid...I asume the docker compose plugin is already installed.you cd into your appdata folder and git cloned the repo cd /mnt/user/appdata/ git clone https://github.com/netbox-community/netbox-docker.gitI've updated the compose with unraids label for easier use on unraid...This requires some pre-made folders for the dockers to be made...Your volumes may need to be fixed as these folder need to exist before you hit compose up... cd /mnt/user/appdata/netbox-docker mkdir netbox mkdir redis mkdir redis-cache mkdir postgress cd netbox mkdir scripts mkdir reports mkdir media cd .. chmod 777 -R * chown nobody:users -R *and the following Compose(This will make a docker bridge network) I have moved the web port, redis port and Postgres port so other tack and docker should not be affect... #version: "3.9" services:netbox: image: docker.io/netboxcommunity/netbox:v4.3-3.3.0 depends_on: - postgres - redis - redis-cache user: "unit:root" healthcheck: test: curl -f http://localhost:8080/login/ || exit 1 start_period: 90s timeout: 3s interval: 15s environment: DB_HOST: postgres DB_NAME: netbox DB_PASSWORD: J5brHrAXFLQSif0K DB_USER: netbox REDIS_HOST: redis REDIS_PASSWORD: H733Kdjndks81 REDIS_DATABASE: 0 REDIS_CACHE_HOST: redis-cache REDIS_CACHE_PASSWORD: t4Ph722qJ5QHeQ1qfu36 REDIS_CACHE_DATABASE: 1 SECRET_KEY: 'r(m)9nLGnz$(_q3N4z1k(EFsMCjjjzx08x9VhNVcfd%6RF#r!6DE@+V5Zk2X' SKIP_SUPERUSER: true WEBHOOKS_ENABLED: true CORS_ORIGIN_ALLOW_ALL: true EMAIL_FROM: [email protected] EMAIL_PORT: 25 EMAIL_SERVER: localhost EMAIL_USERNAME: netbox EMAIL_USE_SSL: false EMAIL_USE_TLS: false GRAPHQL_ENABLED: true HOUSEKEEPING_INTERVAL: 86400 METRICS_ENABLED: false volumes: - ./configuration:/etc/netbox/config:z,rw - netbox-media-files:/opt/netbox/netbox/media - netbox-reports-files:/opt/netbox/netbox/reports - netbox-scripts-files:/opt/netbox/netbox/scripts networks: netbox: ipv4_address: 172.25.0.10 ports: - "60080:8080" labels: net.unraid.docker.webui: "http://[IP]:[PORT:60080]" net.unraid.docker.icon: "https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/netbox-logo.png" folder.view: "netbox" net.unraid.docker.managed: "composeman" netbox-worker: image: docker.io/netboxcommunity/netbox:v4.3-3.3.0 user: "unit:root" depends_on: - postgres - redis - redis-cache command: - /opt/netbox/venv/bin/python - /opt/netbox/netbox/manage.py - rqworker healthcheck: test: ps -aux | grep -v grep | grep -q rqworker || exit 1 start_period: 20s timeout: 3s interval: 15s volumes: - ./configuration:/etc/netbox/config:z,rw - netbox-media-files:/opt/netbox/netbox/media - netbox-reports-files:/opt/netbox/netbox/reports - netbox-scripts-files:/opt/netbox/netbox/scripts networks: netbox: ipv4_address: 172.25.0.11 labels: folder.view: "netbox" net.unraid.docker.icon: "https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/netbox-logo.png" net.unraid.docker.managed: "composeman" netbox-housekeeping: image: docker.io/netboxcommunity/netbox:v4.3-3.3.0 user: "unit:root" depends_on: - postgres - redis - redis-cache command: - /opt/netbox/housekeeping.sh healthcheck: test: ps -aux | grep -v grep | grep -q housekeeping || exit 1 start_period: 20s timeout: 3s interval: 15s volumes: - ./configuration:/etc/netbox/config:z,rw - netbox-media-files:/opt/netbox/netbox/media - netbox-reports-files:/opt/netbox/netbox/reports - netbox-scripts-files:/opt/netbox/netbox/scripts networks: netbox: ipv4_address: 172.25.0.12 labels: folder.view: "netbox" net.unraid.docker.icon: "https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/netbox-logo.png" net.unraid.docker.managed: "composeman" postgres: image: docker.io/postgres:17-alpine environment: POSTGRES_DB: netbox POSTGRES_USER: netbox POSTGRES_PASSWORD: J5brHrAXFLQSif0K healthcheck: test: pg_isready -q -t 2 -d netbox -U netbox start_period: 20s timeout: 30s interval: 10s retries: 5 volumes: - netbox-postgres-data:/var/lib/postgresql/data ports: - "5433:5432" networks: netbox: ipv4_address: 172.25.0.13 labels: net.unraid.docker.icon: "https://raw.githubusercontent.com/sgraaf/Unraid-Docker-Templates/main/postgresql16/icon.png" folder.view: "netbox" net.unraid.docker.managed: "composeman" redis: image: docker.io/valkey/valkey:8.1-alpine command: - sh - -c - valkey-server --appendonly yes --requirepass $$REDIS_PASSWORD environment: REDIS_PASSWORD: H733Kdjndks81 healthcheck: &redis-healthcheck test: '[ $$(valkey-cli --pass "$${REDIS_PASSWORD}" ping) = ''PONG'' ]' start_period: 5s timeout: 3s interval: 1s retries: 5 volumes: - netbox-redis-data:/data ports: - "6380:6379" networks: netbox: ipv4_address: 172.25.0.14 labels: net.unraid.docker.icon: "https://raw.githubusercontent.com/A75G/docker-templates/master/templates/icons/redis.png" folder.view: "netbox" net.unraid.docker.managed: "composeman" redis-cache: image: docker.io/valkey/valkey:8.1-alpine command: - sh - -c - valkey-server --requirepass $$REDIS_PASSWORD environment: REDIS_PASSWORD: t4Ph722qJ5QHeQ1qfu36 healthcheck: *redis-healthcheck volumes: - netbox-redis-cache-data:/data ports: - "6381:6379" networks: netbox: ipv4_address: 172.25.0.15 labels: net.unraid.docker.icon: "https://raw.githubusercontent.com/A75G/docker-templates/master/templates/icons/redis.png" folder.view: "netbox" net.unraid.docker.managed: "composeman" volumes:netbox-media-files: driver: local driver_opts: type: none device: /mnt/user/appdata/netbox-docker/netbox/media o: bindnetbox-reports-files: driver: local driver_opts: type: none device: /mnt/user/appdata/netbox-docker/netbox/reports o: bindnetbox-scripts-files: driver: local driver_opts: type: none device: /mnt/user/appdata/netbox-docker/netbox/scripts o: bindnetbox-postgres-data: driver: local driver_opts: type: none device: /mnt/user/appdata/netbox-docker/postgress o: bindnetbox-redis-data: driver: local driver_opts: type: none device: /mnt/user/appdata/netbox-docker/redis o: bindnetbox-redis-cache-data: driver: local driver_opts: type: none device: /mnt/user/appdata/netbox-docker/redis-cache o: bind #You can docker network create your own or have compose make the docker bridge network and destorey and kill the docker briedge nuetwrok at each compose up/down...#networks:# netbox:# external: true networks:netbox: driver: bridge ipam: config: - subnet: 172.25.0.0/16 # Different subnet from Unraid's default Docker bridge gateway: 172.25.0.1Couldn't get this working with port changes and bridge network, post for a solution for others following the netbox community.... Learn to read and folow the entire post...
May 22, 20251 yr 58 minutes ago, gurulee said:There was no mention to clone the repo outside of just installing the Netbox docker from the app store.The compose for Netbox is correct and is defaulted to '/mnt/cache/appdata/netbox'This is how I'm going into the console of Netbox, pretty straight forward ;-)it in the Compose post...I don't have a way to add them all to CA.This doesn't use the CA docker...Compose only... I can't help you if you don't read and follow in the compose post which is the netbox maintainers dockers and setup.After getting this working, I found that this doesn't fit my needs. And moved on to a different project on my pate... and different documentation docker...
November 26, 2025Nov 26 Hello all, it seems there are issues with this netbox template. I’ve got NetBox working, but I have a problem with the media directory. The first log entry after starting the NetBox docker isfind: ‘/config/media’: Symbolic link loop chown: cannot dereference '/config/media': Symbolic link loop **** Permissions could not be set. This is probably because your volume mounts are remote or read-only. **** **** The app may not work properly and we will not provide support for it. ****in my appdata folder I see:root@tower:/mnt/user/appdata/netbox# ls -l total 16 -rw-r--r-- 1 nobody users 11659 Nov 26 21:42 configuration.py -rw-r--r-- 1 nobody users 0 Nov 26 21:47 ldap_config.py lrwxrwxrwx 1 root root 13 Nov 26 21:45 media -> /config/media drwxr-xr-x 1 nobody users 0 Nov 26 21:42 scripts/My docker run command for NetBox looks like this:docker run -d --name='netbox' --net='netbox_net' --pids-limit 2048 -e TZ="Europe/London" -e HOST_OS="Unraid" -e HOST_HOSTNAME="tower" -e HOST_CONTAINERNAME="netbox" -e 'SUPERUSER_EMAIL'='[email protected]' -e 'SUPERUSER_PASSWORD'='secret_password' -e 'ALLOWED_HOST'='netbox.mydonmain.uk' -e 'DB_NAME'='netbox_db' -e 'DB_USER'='netbox_db_user' -e 'DB_PASSWORD'='secret_password' -e 'DB_HOST'='netbox-postgresql18' -e 'REDIS_HOST'='netbox-redis' -e 'REDIS_DB_TASK'='0' -e 'REDIS_DB_CACHE'='1' -e 'BASE_PATH'='' -e 'REMOTE_AUTH_ENABLED'='' -e 'REMOTE_AUTH_BACKEND'='' -e 'REMOTE_AUTH_HEADER'='' -e 'REMOTE_AUTH_AUTO_CREATE_USER'='' -e 'REMOTE_AUTH_DEFAULT_GROUPS'='' -e 'REMOTE_AUTH_DEFAULT_PERMISSIONS'='' -e 'PUID'='99' -e 'PGID'='100' -e 'UMASK'='022' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.icon='https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/netbox-logo.png' -p '8001:8000/tcp' -v '/mnt/user/appdata/netbox':'/config':'rw' 'lscr.io/linuxserver/netbox'My docker run command for Postgres is:docker run -d --name='netbox-postgresql18' --net='netbox_net' --pids-limit 2048 -e TZ="Europe/London" -e HOST_OS="Unraid" -e HOST_HOSTNAME="tower" -e HOST_CONTAINERNAME="netbox-postgresql18" -e 'POSTGRES_PASSWORD'='secret_password' -e 'POSTGRES_USER'='netbox_db_user' -e 'POSTGRES_DB'='netbox_db' -e 'TZ'='Europe/London' -e 'CA_TS_FALLBACK_DIR'='/var/lib/postgresql' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.icon='https://raw.githubusercontent.com/Skylinar/unraid_templates/refs/heads/main/images/postgresql.png?raw=true' -v '/mnt/user/appdata/netbox-postgresql18':'/var/lib/postgresql':'rw' 'postgres:18'My docker run command for Redis:docker run -d --name='netbox-redis' --net='netbox_net' --pids-limit 2048 -e TZ="Europe/London" -e HOST_OS="Unraid" -e HOST_HOSTNAME="tower" -e HOST_CONTAINERNAME="netbox-redis" -l net.unraid.docker.managed=dockerman -l net.unraid.docker.icon='https://raw.githubusercontent.com/juusujanar/unraid-templates/master/img/Redis-logo.png' 'redis'Does anyone have any idea how I can fix the recursive media folder? Everything seems to be working fine, but I’m sure if I try and add images things will go wrong.
November 26, 2025Nov 26 1 hour ago, Keith Ellis said:Hello Does anyone have any idea how I can fix the recursive media folder? Everything seems to be working fine, but I’m sure if I try and add images things will go wrong.OK, I’ve found a solution. Basically, stop the container, delete the media symlink and recreate a normal ‘media’ directory, start the container.Here is a summary from ChatGPT with a fuller explanation.Solution: NetBox “Symbolic link loop” on /config/media (Unraid +LinuxServer.io)If you see this error when starting the NetBox container:find: ‘/config/media’: Symbolic link loop chown: cannot dereference‘/config/media’: Symbolic link loop **** Permissions could not be set.This is probably because your volume mounts are remote or read-only.****…it’s caused by a recursive symlink created by the LinuxServer.io NetBoxcontainer when running on Unraid’s FUSE-based /mnt/user filesystem.What happened The container creates a symlink:/config/media → /config/mediaBecause /config is mapped to /mnt/user/appdata/netbox, this becomes aloop, and the container can’t set permissions on the folder.Fix 1. Stop the NetBox container 2. Remove the symlink: rm/mnt/user/appdata/netbox/media3. Create a real media folder: mkdir /mnt/user/appdata/netbox/media chown nobody:users /mnt/user/appdata/netbox/media chmod 775 /mnt/user/appdata/netbox/media4. Start the container againAfter that, the container starts cleanly and media uploads worknormally.Why this happens It’s an interaction between: - LinuxServer.io’s startupscript - Unraid’s FUSE filesystem (/mnt/user)This isn’t documented by LSIO or NetBox, but it’s a known behaviour withseveral LSIO containers on Unraid.
January 3Jan 3 I was hoping to get some help. Whenever i start the container and go to the url i get an error:EDIT: I went and created a new docker network and have both containers pointing to that network and still have the same problem.My Netbox compose is: I get the same error when I try to use the official redis dockerdocker run -d --name='netbox' --net='bridge' --pids-limit 2048 -e TZ="America/Chicago" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Tower" -e HOST_CONTAINERNAME="netbox" -e 'SUPERUSER_EMAIL'='[email protected]' # my email -e 'SUPERUSER_PASSWORD'='xxxxxxxxxx' # my password -e 'ALLOWED_HOST'='xxx.xxx.xx.xx' #using my unraid server ip address -e 'DB_NAME'='netbox' -e 'DB_USER'='xxxxxxx' -e 'DB_PASSWORD'='xxxxxxx' -e 'DB_HOST'='xxx.xxx.xx.xx' -e 'DB_PORT'='xxxx' -e 'REDIS_HOST'='xxx.xxx.xx.xx' # using my unraid server address -e 'REDIS_PORT'='6380' # using the a75g redis repo so I assign it 6380 because I already had the official redis install -e 'REDIS_PASSWORD'='xxxxxxxxxxx' # my redis password -e 'REDIS_DB_TASK'='0' -e 'REDIS_DB_CACHE'='1' -e 'BASE_PATH'='' -e 'REMOTE_AUTH_ENABLED'='' -e 'REMOTE_AUTH_BACKEND'='' -e 'REMOTE_AUTH_HEADER'='' -e 'REMOTE_AUTH_AUTO_CREATE_USER'='' -e 'REMOTE_AUTH_DEFAULT_GROUPS'='' -e 'REMOTE_AUTH_DEFAULT_PERMISSIONS'='' -e 'PUID'='99' -e 'PGID'='100' -e 'UMASK'='022' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://xxx.xxx.xx.xx:8003/' -l net.unraid.docker.icon='https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/netbox-logo.png' -p '8003:8000/tcp' -v '/mnt/user/appdata/netbox':'/config':'rw' 'lscr.io/linuxserver/netbox' My redis compse is:docker run -d --name='redis-a75g-repo' --net='bridge' --pids-limit 2048 -e TZ="America/Chicago" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Tower" -e HOST_CONTAINERNAME="redis-a75g-repo" -e 'ALLOW_EMPTY_PASSWORD'='no' -e 'REDIS_PASSWORD'='xxxxxxxxxxx' -e 'REDIS_EXTRA_FLAGS'='--auto-aof-rewrite-percentage 100 --auto-aof-rewrite-min-size 64mb' -e 'CA_TS_FALLBACK_DIR'='/bitnami/redis' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.icon='https://raw.githubusercontent.com/A75G/docker-templates/master/templates/icons/redis.png' -p '6380:6379/tcp' -v '/mnt/user/appdata/redis':'/bitnami/redis':'rw' 'bitnamisecure/redis:latest' Edited January 3Jan 3 by ziamajr
January 3Jan 3 16 hours ago, ziamajr said:I was hoping to get some help. Whenever i start the container and go to the url i get an error:EDIT: I went and created a new docker network and have both containers pointing to that network and still have the same problem.My Netbox compose is: I get the same error when I try to use the official redis dockerdocker run-d--name='netbox'--net='bridge'--pids-limit 2048-e TZ="America/Chicago"-e HOST_OS="Unraid"-e HOST_HOSTNAME="Tower"-e HOST_CONTAINERNAME="netbox"-e 'SUPERUSER_EMAIL'='[email protected]' # my email-e 'SUPERUSER_PASSWORD'='xxxxxxxxxx' # my password-e 'ALLOWED_HOST'='xxx.xxx.xx.xx' #using my unraid server ip address-e 'DB_NAME'='netbox'-e 'DB_USER'='xxxxxxx'-e 'DB_PASSWORD'='xxxxxxx'-e 'DB_HOST'='xxx.xxx.xx.xx'-e 'DB_PORT'='xxxx'-e 'REDIS_HOST'='xxx.xxx.xx.xx' # using my unraid server address-e 'REDIS_PORT'='6380' # using the a75g redis repo so I assign it 6380 because I already had the official redis install-e 'REDIS_PASSWORD'='xxxxxxxxxxx' # my redis password-e 'REDIS_DB_TASK'='0'-e 'REDIS_DB_CACHE'='1'-e 'BASE_PATH'=''-e 'REMOTE_AUTH_ENABLED'=''-e 'REMOTE_AUTH_BACKEND'=''-e 'REMOTE_AUTH_HEADER'=''-e 'REMOTE_AUTH_AUTO_CREATE_USER'=''-e 'REMOTE_AUTH_DEFAULT_GROUPS'=''-e 'REMOTE_AUTH_DEFAULT_PERMISSIONS'=''-e 'PUID'='99'-e 'PGID'='100'-e 'UMASK'='022'-l net.unraid.docker.managed=dockerman-l net.unraid.docker.webui='http://xxx.xxx.xx.xx:8003/'-l net.unraid.docker.icon='https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/netbox-logo.png'-p '8003:8000/tcp'-v '/mnt/user/appdata/netbox':'/config':'rw' 'lscr.io/linuxserver/netbox'My redis compse is:docker run -d --name='redis-a75g-repo' --net='bridge' --pids-limit 2048 -e TZ="America/Chicago" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Tower" -e HOST_CONTAINERNAME="redis-a75g-repo" -e 'ALLOW_EMPTY_PASSWORD'='no' -e 'REDIS_PASSWORD'='xxxxxxxxxxx' -e 'REDIS_EXTRA_FLAGS'='--auto-aof-rewrite-percentage 100 --auto-aof-rewrite-min-size 64mb' -e 'CA_TS_FALLBACK_DIR'='/bitnami/redis' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.icon='https://raw.githubusercontent.com/A75G/docker-templates/master/templates/icons/redis.png' -p '6380:6379/tcp' -v '/mnt/user/appdata/redis':'/bitnami/redis':'rw' 'bitnamisecure/redis:latest'Hello,I've just compared our docker run commands and note the following:Netbox:Since you are using a custom docker network you can reference the Postgres and Redis containers by hostname, you don't need to use IP address or port number. The hostname of the docker is the Container Name in the Docker template. I note your docker run commands are not using a custom docker network, but I suspect you changed this after the initial post.So -e 'DB_HOST'='xxx.xxx.xx.xx'can be-e 'DB_HOST'='netbox-postgresql18'obviously change this to your Container name. For this to work, your Postgres container must be on the same custom docker network.-e 'DB_PORT'='xxxx' can be deleted from the template, you probably need to enable 'advanced' mode to do this at the top right of the docker template form.The same for -e 'REDIS_HOST' Change this to your Redis container name and delete-e 'REDIS_PORT'-e 'REDIS_PASSWORD'Since the Redis container is only available on the Netbox custom docker network and we are removing the Port, only containers inside this custom docker network can access Redis, so I think it is safe to remove the password. This is what solves your Authentication issues.REDISYou have a lot more defined in your Redis Docker template. I think I deleted a lot here.Try deleting the following from your template: -e 'ALLOW_EMPTY_PASSWORD'='no' -e 'REDIS_PASSWORD'='xxxxxxxxxxx'I think deleting the password bits will solve your authentication issue.I also do not have the following, but not sure this is an issue: -e 'REDIS_EXTRA_FLAGS'='--auto-aof-rewrite-percentage 100 --auto-aof-rewrite-min-size 64mb' -e 'CA_TS_FALLBACK_DIR'='/bitnami/redis'Give this ago, let me know how you get on.cheers.Keith. Edited January 3Jan 3 by Keith Ellis
January 5Jan 5 @Keith Ellis so I took your advise and pretty much started all over, new network, new dockers and used the official redis docker so didn't require authentication and after after a couple of tries, it just works. I have no idea what what going on. Thank you again for the response.
May 27May 27 Is it just me? or is anyone else finding that making changes to the docker with Edit does NOT result in a modification to the configuration.py file? I feel like if I had done everything right the first time, it would have worked off the bat.Instead I had to use VI to edit the file inside the docker console until I got it right.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.