Not familiar with netbox, so there may be nuance that I’m likely to miss. But I guess the first thing to do is understand exactly what you have. Are your containers deployed using docker compose? If so, just copy the compose file over to the new host, then docker compose up -d and your container stack should be running just the same. If your not using compose yet, there’s a tool that can generate a compose file from running docker containers. That could make life easier.
The possibly more complicated bit is any persistent data - where is this? Is it in bind mounts on the host? Or volume mounts? Things like secrets and configuration will also need to be copied over and put in the right places, as just a compose file alone will only get you a greenfield setup
Not familiar with netbox, so there may be nuance that I’m likely to miss. But I guess the first thing to do is understand exactly what you have. Are your containers deployed using docker compose? If so, just copy the compose file over to the new host, then docker compose up -d and your container stack should be running just the same. If your not using compose yet, there’s a tool that can generate a compose file from running docker containers. That could make life easier.
The possibly more complicated bit is any persistent data - where is this? Is it in bind mounts on the host? Or volume mounts? Things like secrets and configuration will also need to be copied over and put in the right places, as just a compose file alone will only get you a greenfield setup