Containers stuck status STARTING

[nortuzar]

Containers stuck status STARTING

[marcel-dancak]

I'm not really sure what is the reason for PWD environment variable not being set on Ubuntu. Maybe it's when you run this command as root user with sudo. Often it's easier to add docker group to your user account. But anyway, you can also edit your docker-compose.yml and change path with PWD variable to resolved absolute path.

[nortuzar]

Thanks for the reply. I start over following a guide to add the user to docker group and that fixed the problem. Now i´m dealing with the qgis plugin, because I made a mistake with the information, and now I cant modify the info, so everytime it shows WARNING: failed to connect

[marcel-dancak]

Probably it's just not very obvious, but you can edit your login information from QGIS menu Web -> Gisquick -> Configure
I will consider showing login dialog automatically after failed attempt, or saving account credentials only after successful connection.

[nortuzar]

Probably it's just not very obvious, but you can edit your login information from QGIS menu Web -> Gisquick -> Configure I will consider showing login dialog automatically after failed attempt, or saving account credentials only after successful connection.

Wow thanks for the quick reply, my bad there..

I tried to build from scratch but now I run
docker compose up -d without problem. But then after running docker compose exec app gisquick migrate up
i receive the message
Error response from daemon: Container e23f00363f8bb3d0dd41ab950f2595404b100c3f159cb1f198453df0b907a6d9 is restarting, wait until the container is running
I understand this is the container gisquick-app-1 from the gisquick/server image. I try stop, restart, but nothing, I can remember why in my last try everything works

[marcel-dancak]

If it's app service failing, you can try to get more info from logs. This command should work

docker compose logs --tail=200 app