[Bug][Module Name] Docker doesn't work anymore after upgrading - stuck with 502

[gabrielenosso]

Search before asking

• I had searched in the issues and found no similar issues.

What happened

Setup devlake, completed onboarding, added some repo.
Then shut it down (emulating an upgrade), pruned docker container and volume, restarted devlake: Error in Config UI (502)

What do you expect to happen

DevLake would work after restart

How to reproduce

It looks like there's a bug with "onboard", after updating DevLake.
Steps to reproduce:
Setup DevLake and start Docker container (sudo docker-compose restart)
Stop Docker container (sudo docker-compose down)
Remove old containers to clean up (sudo docker system prune -a --volumes)
Start again Docker container (sudo docker-compose up -d)
Docker Config UI will then not be accessible anymore, always showing error, for a request to the API (request to http://ip:4000/api/store/onboard gives 502)

Dropping the "lake" DB and restarting the docker container makes everything work.

Anything else

No response

Version

1.0.5 beta

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[klesh]

@gabrielenosso I'm confused, why did you prune the volumes after docker-compose down? Wouldn't it delete the databases ? or are you using an external database?

[d4x1]

Thank you for your feedback. We'll take a look at it.

[gabrielenosso]

@klesh I am using an external DB indeed, for both Grafana and DevLake.

I am trying to setup the whole solution as a test for my company. So I'm testing also the upgrade.

[klesh]

@gabrielenosso Hi, thanks for the reply. May I ask which version did you upgrade from?
Would you like to share some screenshots to help us understand what was wrong? Especialloy the API request since I am trying to reproduce the problem but I find it hard to understand.
Here is how I proceed for an upgrade:

1. docker compose down
2. modify the docker-compose.yml from an old version to a newer one
3. docker compose up -d

So, I am confused by the prune part and I would need the older version. Did you finish the onboard procedure before the upgrade or which step was it?

[gabrielenosso]

I finished the onboard procedure.
I pruned the volumes to reset the complete state of the app, as I am using external DBs for Grafana and for DevLake itself.
I did the pruning to clean space in the VM.

Unfortunately I can't share screenshots at the moment, as our IT department is working on the VM itself.