Upgrading Docker Image

[johncadengo]

I noticed a new version recently came out: v0.0.8.

Here is what I had to do, given my docker compose file, to upgrade it:

$ docker compose pull
$ docker compose up -d

When I simply pulled and recreated the image, I was stuck on an infinite loading screen.

So, I realized the docker image might have something to do with it. This is why I suggested not to include this in the docker compose file:

  volumes:
    - ./app:/app

If you include the above in the file, it will persist the app folder from the first time you initialize the container. So if you initialized the container on v0.0.7, then you can't upgrade to v0.0.8.

I hadn't included that, though, what I had was more along the lines of this:

    volumes:
      - ./static:/app/static

The issue here is that the JS/CSS files won't be upgraded when you pull the latest image.

@mauran had the right idea from the start, which is only to include the uploaded assets, which is a folder that should persist, but isn't changed by the image with each new version:

    volumes:
      - ./assets:/app/static/upload

So, I want to point out that it's important when persisting data not to persist all the data or else you won't be able to upgrade the image properly.

Lastly, I wanted to write this up to point out that when I do upgrade the image, and it successfully loads, only persisting the /app/static/upload folder, I still have trouble if I was already logged into the website. It will still have an infinite loading screen. So it looks like it didn't upgrade right. But, what I need to do next is to clear my cookies and session data. Once I clear the cookies, I can load the page and login again.

I believe I set the env variables right when it came to session related vars. Assuming those are correctly set, is there a bug when upgrading and/or bringing down the container and spinning it back up again? Can anyone reproduce?