Fwd: Update error message

[Kurt H.]

Dear all

I just tried to update my installation to the latest version, but get an error:

docker compose pull

image ticketscad-newui:local  pull access denied for ticketscad-newui, repository does not exist or may require 'docker login'.

Now my system doesn't react any longer, no login screen appears.

Did I miss something?

Thanks 

BR

Kurt

[Eric Osterberg]

Hello Kurt...

Your message and subject line say "Fwd:". Did you start your message somewhere else? This is the first I'm seeing it.

Good news first: nothing you've described touches your data. Neither the command that failed nor the fix below deletes your database, uploads, or keys - those all live on separate Docker volumes that stay put through all of this.

What happened with the pull error:

docker compose pull tries to download images from a registry (Docker Hub). That works fine for the database - mariadb:11 is a real, published image. But the app image, ticketscad-newui:local, is not published anywhere. It only exists because it gets built, on your own machine, from this project's Dockerfile, the first time you ran docker compose up -d --build. Docker Hub has never heard of "ticketscad-newui" and never will - there is nothing there to pull. That's exactly what "pull access denied ... repository does not exist" is telling you: it went looking in the wrong place. You didn't miss a step: docker compose pull just isn't a command this project ever needs.

On why your system stopped responding entirely:

That part I can't be 100% sure of from the pull error alone, since a failed pull by itself doesn't stop or touch any already-running containers. My best guess is that somewhere in trying to sort this out you also ran docker compose down (a completely reasonable instinct - "let me stop everything and start clean") and just haven't brought it back up since. That would explain "no login screen, nothing reacts" perfectly: nothing is running.

To get back to where you were, with nothing at risk, from your ticketscad folder run:

docker compose ps

That shows what's currently up (probably nothing, or just the database). Then:

docker compose up -d

Important: no --build on this step, and do not run docker compose down -v (the -v wipes your data volumes - you don't want that here, and it isn't needed). Plain docker compose up -d reuses the images already sitting on your machine, including the app image you built the first time around, and starts everything back up as it was. Give it a minute, then:

docker compose logs -f app

and try http://<your address>:8081 again.

If that brings the login page back, you're not lost, you're just back on the version you had before. To actually get the newest version, it's the same two commands I gave you back on July 25 when you first got this running - that recipe hasn't changed:

git pull
docker compose up -d --build

The --build is the whole update - it rebuilds the app image from the new code git pull just fetched, and the container applies any database changes on its own when it restarts. There's no separate pull step for the app, ever.

If docker compose up -d does NOT bring it back - for example if the database container won't go healthy - don't guess further, just paste back here the output of:

docker compose ps
docker compose logs db --tail=50
docker compose logs app --tail=50

and we'll sort it out from there. Given everything you've described so far, I'd be surprised if this isn't a two-command fix.

--
You received this message because you are subscribed to the Google Groups "Open Source CAD" group.
To unsubscribe from this group and stop receiving emails from it, send an email to open-source-c...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/open-source-cad/CAGVvMhq1%2BJfo2kzV349V5ToV%2BFnu46GWWesqSRUPARoxVDkQag%40mail.gmail.com.