
11notes/netbox!banner
!size!5px!version!5px!pulls!5px[]([***]
Run NetBox smaller, lightweight and more secure than ever
What can I do with this? This image will give you a rootless and lightweight NetBox installation. NetBox exists to empower network engineers. Since its release in 2016, it has become the go-to solution for modeling and documenting network infrastructure for thousands of organizations worldwide. As a successor to legacy IPAM and DCIM applications, NetBox provides a cohesive, extensive, and accessible data model for all things networked. By providing a single robust user interface and programmable APIs for everything from cable maps to device configurations, NetBox serves as the central source of truth for the modern network.
Why should I run this image and not the other image(s) that already exist? Good question! All the other images on the market that do exactly the same don’t do or offer these options:
If you value security, simplicity and the ability to interact with the maintainer and developer of an image. Using my images is a great start in that direction.
Below you find a comparison between this image and the most used or original one.
| image | 11notes/netbox:4.3.3 | netboxcommunity/netbox:v4.3.3 |
|---|---|---|
| image size on disk | 538MB | 702MB |
| process UID/GID | 1000/1000 | 0/0 |
| distroless? | ❌ | ❌ |
| rootless? | ✅ | ❌ |
yamlname: "netbox" services: postgres: image: "11notes/postgres:16" read_only: true environment: TZ: "Europe/Zurich" POSTGRES_PASSWORD: ${POSTGRES_PASSWORD} volumes: - "postgres.etc:/postgres/etc" - "postgres.var:/postgres/var" - "postgres.cmd:/run/cmd" tmpfs: - "/run/postgresql:uid=1000,gid=1000" - "/postgres/log:uid=1000,gid=1000" networks: backend: restart: "always" cron: depends_on: postgres: condition: "service_healthy" restart: true image: "11notes/cron:4.6" environment: TZ: "Europe/Zurich" CRONTAB: |- 0 3 * * * cmd-socket '{"bin":"backup"}' > /proc/1/fd/1 volumes: - "postgres.cmd:/run/cmd" restart: "always" redis: image: "11notes/redis:7.4.2" environment: REDIS_PASSWORD: ${REDIS_PASSWORD} TZ: "Europe/Zurich" volumes: - "redis.etc:/redis/etc" - "redis.var:/redis/var" networks: backend: restart: always app: depends_on: postgres: condition: "service_healthy" restart: true redis: condition: "service_healthy" restart: true image: "11notes/netbox:4.3.3" environment: TZ: "Europe/Zurich" NETBOX_ADMIN_PASSWORD: ${NETBOX_ADMIN_PASSWORD} volumes: - "etc:/netbox/etc" - "var:/netbox/var" tmpfs: - "/run:uid=1000,gid=1000" ports: - "3000:3000/tcp" networks: frontend: backend: restart: "always" volumes: etc: var: postgres.etc: postgres.var: postgres.cmd: redis.etc: redis.var: networks: frontend: backend: internal: true
| Parameter | Value | Description |
|---|---|---|
user | docker | user name |
uid | 1000 | user identifier |
gid | 1000 | group identifier |
home | /netbox | home directory of user docker |
| Parameter | Value | Default |
|---|---|---|
TZ | Time Zone | |
DEBUG | Will activate debug option for container image and app (if available) |
These are the main tags for the image. There is also a tag for each commit and its shorthand sha256 value.
It is of my opinion that the :latest tag is dangerous. Many times, I’ve introduced breaking changes to my images. This would have messed up everything for some people. If you don’t want to change the tag to the latest semver, simply use the short versions of semver. Instead of using :4.3.3 you can use :4 or :4.3. Since on each new version these tags are updated to the latest version of the software, using them is identical to using :latest but at least fixed to a major or minor version.
If you still insist on having the bleeding edge release of this app, simply use the :rolling tag, but be warned! You will get the latest version of the app instantly, regardless of breaking changes or security issues or what so ever. You do this at your own risk!
docker pull 11notes/netbox:4.3.3 docker pull ghcr.io/11notes/netbox:4.3.3 docker pull quay.io/11notes/netbox:4.3.3
This image is provided to you at your own risk. Always make backups before updating an image to a different version. Check the releases for breaking changes. If you have any problems with using this image simply raise an issue, thanks. If you have a question or inputs please create a new discussion instead of an issue. You can find all my other repositories on github.
created 27.06.2025, 08:20:32 (CET)



manifest unknown 错误
TLS 证书验证失败
DNS 解析超时
410 错误:版本过低
402 错误:流量耗尽
身份认证失败错误
429 限流错误
凭证保存错误
来自真实用户的反馈,见证轩辕镜像的优质服务