I need to update my NetBox, and not sure which route to take.

I use NetBox to manage all my infrastructure data. It’s primarily an IPAM for me, but I also track racks and ports and some wiring. I store serial numbers and console urls and whatnot there too. It’s an important (to me) tool that runs on a docker host with daily backups.

I need to upgrade. I have seen shots of the new version, and boy does it look cool. Talked with another lemming about it yesterday and decided to figure out my pathway.

---

The choice.
Do I in-place upgrade (their way), or do I deploy a new one and migrate the data to it?

The challenge.
See … this is embarrassing. I’m a professional virtualization guy, that’s how I pay my bills. But I’m barely proficient with docker. So yes, I run NetBox on a docker system that I configured from scratch, but I lack real confidence in what I’m doing in that environment.

---

NetBox-docker Upgrade
https://github.com/netbox-community/netbox-docker/wiki/Updating

I am afraid that if I follow the directions for an in-place upgrade, I’m risking my data. Docker is just not my thing, and I feel I might screw it up.

---

NetBox Migrate Data
https://github.com/netbox-community/netbox/discussions/14104

But lift-and-shift some data to a new (upgraded) system?
I do that sort of thing quite a bit. I’m pretty darn comfortable with deploying migrated data to a pre-prod, testing it, and then cutting over.
That sounds like a normal day at work.

---

Just to note … NetBox is capable of much more than I use it for. Its designed to expose and update its data via API for other apps to use and modify. I only access it via the GUI to track my infra. I say this bit just because that simplifies questions about the upgrade, in that there are no external links to consider. It’s a stand-alone system, talks to nothing else.

So … yet another long-ass post about my lab.
I’d welcome any input, however tangentially related. Thanks!