netbox-docker VS docker-autocompose

Hi everyone. Im new to netbox, im trying to install netbox docker and i'm following this guide: https://github.com/netbox-community/netbox-docker

Hi, I'm failing big time to deploy the official netbox docker-compose on Portainer. I love Portainer and I would like to have netbox as a stack on Portainer. But I can't make it work even spending more than just a couple of evenings. I have forked the repo and used it to deploy from the git repo, using additional paths for docker-compose. override.yml

I'm a bit of a newbie in netbox, I'm using the docker installation as per GitHub - netbox-community/netbox-docker: 🐳 Docker Image of NetBox

Here is netbox's compose file: https://github.com/netbox-community/netbox-docker/blob/relea... -- there is no way I am going to spend the time to translate that into whatever k8s wants. If it isn't broken don't fix it.

git clone -b release https://github.com/netbox-community/netbox-docker.git cd netbox-docker tee docker-compose.override.yml <

Did you check the Github repo?

But if you’re looking to back up the db, the reccomended way to do this is to dump the db to a file and backup that. Instructions are in the project wiki

Reposting from GitHub's Discussion: https://github.com/netbox-community/netbox-docker/discussions/884

Easiest way to run Netbox with Docker is to use the community project on github https://github.com/netbox-community/netbox-docker

But there is this little tool docker-autocompose that can read the configuration of your current containers and export that into a docker-compose.yml. It probably wont work 100% perfect for every possible container config, but its worth a try and it might save a lot of time when making the switch from run to compose. Good luck!

You can try to use docker-autocompose to read the configs of your currently deployed containers and write them into a compose file for you.

There are different registries, Docker Hub, Quay (quay.io), GitHub (ghcr.io), Linuxserver (lscr.io). Then there is the image name and then the tag (//:; for example lscr.io/linuxserver/plex:latest). The tag and the registry won't matter too much for you (tag I guess you use latest), because most maintainers like Linuxserver push the same image to different registries. So it doesn't really matter if you use lscr.io/linuxserver/plex:latest or just linuxserver/plex:latest or ghcr.io/linuxserver/plex:latest. What does matter is if you use the linxserver or the plexinc image. If you run docker container ls in your terminal, you can see which image you are using. You could then run docker container inspect to get a json config of your plex container and volume mounts etc. to use that to create a docker compose file for it. There are also tools that do that automatically for you, like this: https://github.com/Red5d/docker-autocompose/blob/master/README.md This way, you can use docker compose to start/stop/update and have a permanent config which you can easily migrate to a new NAS/server.

Run this https://github.com/Red5d/docker-autocompose

Here is the link to docker-autocompose for those that might be able to help. https://github.com/Red5d/docker-autocompose

I converted existing docker run via https://www.composerize.com/ (since I had them written down in text file) , you can also use https://github.com/Red5d/docker-autocompose (examples on very bottom) to convert existing containers to YML file.