Docker Upgrade - Installation Page

10 mesi tempo fa
I have nopCommerce installed in Azure Web App for Containers. I have the App_Data path mounted which contains the appropriate appSettings.json.

I tried updating from 4.50.1 to 4.50.2 this morning, and now I'm stuck with the installation screen.

Can anyone point me to what it's checking before forwarding me to the Installation page? On 4.50.1 I had restarted my container multiple times and it had no issue reading from the mount path before.

I tried re-assigning the mounted paths as well to see if it was a bug there, but no dice.
10 mesi tempo fa
For what it's worth - I dropped the version back to 4.50.1 and I got my Store page again.

Is this a bug with 4.50.2 ? Anyone else replicate?
10 mesi tempo fa
Not seeing anything directly related in commits. Will need to do more testing.

Does nopCommerce check for simply the presence of App_Data/appsettings.json in order to determine showing Installation page?
9 mesi tempo fa
I reproduced the same error by updating to version 4.50.2. The App_Data/appsettings.json file is present. After the downgrade to version 4.50.1 everything is back to working.

I have an error I think related: by installing version 4.50.2 from scratch I can't see any files inside the docker volume folder (but the website is working).

This is the relevant part of my docker-compose file that worked:

        image: nopcommerceteam/nopcommerce:4.50.2
        container_name: nop
        restart: always
            - appdata:/app
            - internal
            - web    
            - "5000:80"              
            - db  

Maybe something have changed permission-wise with the new version?
9 mesi tempo fa
I just inspected the image layers of the tag latest (the same as 4.50 and 4.50.2)

and the tag 4.50.1

there are some missing lines after the 14th layer, the error is probably the missing WORKDIR /app
9 mesi tempo fa
Was this Dockerfile used during the push of the 4.50.2 image - even though it has a GitHub diff of only 6 days ago?
9 mesi tempo fa
We updated the image on the dockerhub and returned the file system structure in accordance with previous versions. For more details please see the PR from Mitch Barry.
9 mesi tempo fa
Thanks, I was able to update to the newly deployed 4.50.2 image without issue!