Starting and stopping

[4jag]

What should I do when containers are stuck "restarting"? I'm sorry if this is really a docker question vs Inventree.

I'm testing in WSL 2 & Docker-Desktop. (It's also a personal workstation, so I need to shut it down restart frequently).

When I first got Inventree running for the first time looks like the first PS below.
Since Docker-desktop's UI doesn't refresh the list of images and containers, I restarted docker desktop. But this took down the whole docker environment. I'm trying to restart with docker-compose down , docker-compose up -d but the state of worker and server remain "Restarting..."

How would I tear down the containers and start over, and
What is the normal way of shutting down and restarting when using Docker-desktop.
Also does anyone know how to force Docker-desktop into refreshing it's UI data?

(env) ~/inventree/docker$ docker ps
CONTAINER ID   IMAGE                        COMMAND                  CREATED         STATUS         PORTS                     NAMES
2e48177a46c8   nginx:stable                 "/docker-entrypoint.…"   2 minutes ago   Up 2 minutes   0.0.0.0:1337->80/tcp      inventree-proxy
cbcd68e2be54   inventree/inventree:stable   "/bin/bash ../docker…"   2 minutes ago   Up 2 minutes                             inventree-worker
ff4a08611aae   inventree/inventree:stable   "/bin/bash ../docker…"   2 minutes ago   Up 2 minutes   8000/tcp                  inventree-server
76dad38da0e6   postgres:13                  "docker-entrypoint.s…"   2 minutes ago   Up 2 minutes   0.0.0.0:62546->5432/tcp   inventree-db

Upon restarting it looks like this:

(env) ~/inventree/docker$ docker ps
CONTAINER ID   IMAGE                        COMMAND                  CREATED         STATUS                          PORTS                     NAMES
03f2ab13b5df   inventree/inventree:stable   "/bin/bash ../docker…"   5 minutes ago   Restarting (1) 29 seconds ago                             inventree-worker
81fb81c2b007   nginx:stable                 "/docker-entrypoint.…"   5 minutes ago   Up 5 minutes                    0.0.0.0:1337->80/tcp      inventree-proxy
c35900afc160   inventree/inventree:stable   "/bin/bash ../docker…"   5 minutes ago   Restarting (1) 31 seconds ago                             inventree-server
3aaf401d296e   postgres:13                  "docker-entrypoint.s…"   5 minutes ago   Up 5 minutes                    0.0.0.0:62703->5432/tcp   inventree-db

NGINX Port question:
Lastly, when I first ran docker-compose run inventree-server invoke update I did so with nginx.conf set with server { listen 8022; since I run a lot of other projects on this workstation and ports 80, 8000 are in use. When I started Inventree I didn't get a response on 8022. I returned it to listen:80 to see if I get something, but by now I have the 'Restarting' issue above going on. ?

Thanks

[SchrodingersGat]

Regarding the restarting issue - can you grab the logs from the server and worker containers? There must be something going on there.

Regarding the nginx issue:

• Did you only change the port number in the nginx config file?
• Did you restart the docker-compose setup after doing this?

[4jag]

Do you mean this?

volumes:
    # NOTE: Change /path/to/data to a directory on your local machine
    # Persistent data, stored external to the container(s)
    data:
        driver: local
        driver_opts:
            type: none
            o: bind
            # This directory specified where InvenTree data are stored "outside" the docker containers
            # Change this path to a local system path where you want InvenTree data stored
            device: /home/inventree/data

[SchrodingersGat]

So the path specified under "device" must refer to your local (computer) filesystem.. Do you have a local directory called /home/inventree/data?

Note; this is different to the /home/inventree/data internal to the docker container, and does not have to be at that specific path

[4jag]

This in on WSL 2 Ubuntu on a Windows10 PC. So this would mean /home/inventree/data exists in the WSL 2 environment, right? (not the Win10 PC). If yes, then that's the ubuntu account running the docker stuff.
I'm not sure what caused the permission denied errors since the data and static folder were writable and there wasn't a config.yaml file already in it, but for some reason root owned /home/inventree/data/pgdb, and after deleting all the cruft in user inventree's home dir I was able to rebuild the production docker load. (I must have attempted a development build in this folder prior, since the was a "src" folder tree there.

[SchrodingersGat]

This "device" path must point to a writeable directory on your Win10 PC

[4jag]

When I say /home/inventree I'm referring to the WSL user's folder, not a folder inside the container. I suspect that inside the inventree-server container you're using the same username "inventree" ...

inventree:~$ docker exec -it 4a69dc9aa7e1 /bin/bash
bash-5.1$ pwd
/home/inventree/InvenTree
bash-5.1$ echo $HOME
/home/inventree
bash-5.1$

Yup -- I should have made user daffyduck to be less confusing (sorry, I had first followed instructions for building a dev server, so named my WSL user "inventree"). So, now it's just a coincidence that I'm running docker outside in WSL as the same usernames that are inside the server containers.

[4jag]

Ok so knowing the container IDs:

$ docker ps
CONTAINER ID   IMAGE                        COMMAND                  CREATED        STATUS          PORTS                     NAMES
1cc634f0cba7   nginx:stable                 "/docker-entrypoint.…"   10 hours ago   Up 34 seconds   0.0.0.0:1337->80/tcp      inventree-proxy
593ad334a3ed   inventree/inventree:stable   "/bin/bash ../docker…"   10 hours ago   Up 39 seconds                             inventree-worker
4a69dc9aa7e1   inventree/inventree:stable   "/bin/bash ../docker…"   10 hours ago   Up 40 seconds   8000/tcp                  inventree-server
30456f6693c9   postgres:13                  "docker-entrypoint.s…"   10 hours ago   Up 36 seconds   0.0.0.0:57065->5432/tcp   inventree-db

I can shutdown the system via:

$ docker stop 4a69dc9aa7e1 593ad334a3ed 30456f6693c9 1cc634f0cba7
4a69dc9aa7e1
593ad334a3ed
30456f6693c9
1cc634f0cba7

Then after quiting Docker-desktop and shutting-down/reboot the PC for a while, restart by Starting Docker-desktop, then:

$ docker start 4a69dc9aa7e1 593ad334a3ed 30456f6693c9 1cc634f0cba7
4a69dc9aa7e1
593ad334a3ed
30456f6693c9
1cc634f0cba7