netboxcommunity/netbox!GitHub closed pull requests !Github release workflow !Docker Pulls
The GitHub repository houses the components needed to build NetBox as a container. Images are built regularly using the code in that repository and are pushed to Docker Hub, Quay.io and GitHub Container Registry.
Do you have any questions?
Before opening an issue on Github,
please join our Slack and ask for help in the #netbox-docker channel.
To get NetBox Docker up and running run the following commands. There is a more complete Getting Started guide on our wiki which explains every step.
bashgit clone -b release [***] cd netbox-docker tee docker-compose.override.yml <<EOF version: '3.4' services: netbox: ports: - 8000:8080 EOF docker compose pull docker compose up
The whole application will be available after a few minutes.
Open the URL [***] in a web-browser.
You should see the NetBox homepage.
To create the first admin user run this command:
bashdocker compose exec netbox /opt/netbox/netbox/manage.py createsuperuser
If you need to restart Netbox from an empty database often, you can also set the SUPERUSER_* variables in your docker-compose.override.yml as shown in the example.
New container images are built and published automatically every ~24h.
We recommend to use either the
vX.Y.Z-a.b.ctags or thevX.Y-a.b.ctags in production!
vX.Y.Z-a.b.c, vX.Y-a.b.c:
These are release builds containing NetBox version vX.Y.Z.
They contain the support files of NetBox Docker version a.b.c.
You must use NetBox Docker version a.b.c to guarantee the compatibility.
These images are automatically built from the corresponding releases of NetBox.latest-a.b.c:
These are release builds, containing the latest stable version of NetBox.
They contain the support files of NetBox Docker version a.b.c.
You must use NetBox Docker version a.b.c to guarantee the compatibility.
These images are automatically built from the master branch of NetBox.snapshot-a.b.c:
These are prerelease builds.
They contain the support files of NetBox Docker version a.b.c.
You must use NetBox Docker version a.b.c to guarantee the compatibility.
These images are automatically built from the develop branch of NetBox.For each of the above tag, there is an extra tag:
vX.Y.Z, vX.Y:
This is the same version as vX.Y.Z-a.b.c (or vX.Y-a.b.c, respectively).
It always points to the latest version of NetBox Docker.latest
This is the same version as latest-a.b.c.
It always points to the latest version of NetBox Docker.snapshot
This is the same version as snapshot-a.b.c.
It always points to the latest version of NetBox Docker.Please refer to our wiki on GitHub for further information on how to use the NetBox Docker image properly. The wiki covers advanced topics such as using files for secrets, configuring TLS, deployment to Kubernetes, monitoring and configuring LDAP.
Our wiki is a community effort. Feel free to correct errors, update outdated information or provide additional guides and insights.
Feel free to ask questions in our GitHub Community
or join our Slack and ask in our channel #netbox-docker,
which is free to use and where there are almost always people online that can help you in the Slack channel.
If you need help with using NetBox or developing for it or against it's API
you may find the #netbox channel on the same Slack instance very helpful.
This project relies only on Docker and docker-compose meeting these requirements:
20.10.10.1.5.6.1.28.0.To check the version installed on your system run docker --version and docker compose version.
Please read the release notes carefully when updating to a new image version. Note that the version of the NetBox Docker container image must stay in sync with the code.
If you update for the first time, be sure to follow our How To Update NetBox Docker guide in the wiki.
./build.sh can be used to rebuild the container image. See ./build.sh --help for more information.
For more details on custom builds consult our wiki.
We have a test script. It runs NetBox's own unit tests and ensures that all initializers work:
bashIMAGE=netboxcommunity/netbox:latest ./test.sh
This repository is currently maintained by the community. Please consider sponsoring the maintainers of this project.
探索更多轩辕镜像的使用方法,找到最适合您系统的配置方式
通过 Docker 登录认证访问私有仓库
在 Linux 系统配置镜像服务
在 Docker Desktop 配置镜像
Docker Compose 项目配置
Kubernetes 集群配置 Containerd
K3s 轻量级 Kubernetes 镜像加速
在宝塔面板一键配置镜像
Synology 群晖 NAS 配置
飞牛 fnOS 系统配置镜像
极空间 NAS 系统配置服务
爱快 iKuai 路由系统配置
绿联 NAS 系统配置镜像
QNAP 威联通 NAS 配置
Podman 容器引擎配置
HPC 科学计算容器配置
ghcr、Quay、nvcr 等镜像仓库
无需登录使用专属域名
需要其他帮助?请查看我们的 常见问题Docker 镜像访问常见问题解答 或 提交工单
免费版仅支持 Docker Hub 访问,不承诺可用性和速度;专业版支持更多镜像源,保证可用性和稳定速度,提供优先客服响应。
专业版支持 docker.io、gcr.io、ghcr.io、registry.k8s.io、nvcr.io、quay.io、mcr.microsoft.com、docker.elastic.co 等;免费版仅支持 docker.io。
当返回 402 Payment Required 错误时,表示流量已耗尽,需要充值流量包以恢复服务。
通常由 Docker 版本过低导致,需要升级到 20.x 或更高版本以支持 V2 协议。
先检查 Docker 版本,版本过低则升级;版本正常则验证镜像信息是否正确。
使用 docker tag 命令为镜像打上新标签,去掉域名前缀,使镜像名称更简洁。
来自真实用户的反馈,见证轩辕镜像的优质服务