It's happening on a fresh install of the docker container, so no data. Just downloaded the image and started it without mapping any drives
On Monday, September 23, 2024 at 10:43:10 PM UTC-6 Chad Wilson wrote: > Maybe you can share the specific lines it gets stuck on, and something of > your environment (OS, container runtime version etc)? Doing anything > unusual with volume mounts or entry points or a custom container image? > > If you are upgrading an existing install perhaps there is a lock that's > stuck on your database? > > The containers are all automatically tested that they start up correctly > within latest Docker on Linux (albeit in a docker-in-docker type of > environment) and within Kubernetes versions and they also work OK for me on > MacOS within Colima/Docker. > > On Tue, 24 Sept 2024, 04:49 Lawrence, <[email protected]> wrote: > >> Anyone else stuck on upgrading database on a fresh install of the docker >> container? I'm able to run v24.2.0 container no problem, but v24.3.0 didn't >> complete after an hour. >> >> This could be a me problem, but not sure what I could have done since I >> just downloaded the image and started it. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "go-cd" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/go-cd/caf591ea-eeb8-4745-a875-779860a2bf8an%40googlegroups.com >> >> <https://groups.google.com/d/msgid/go-cd/caf591ea-eeb8-4745-a875-779860a2bf8an%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- You received this message because you are subscribed to the Google Groups "go-cd" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/go-cd/59548a9e-5ff1-4707-babc-1ebff7527fb0n%40googlegroups.com.
