2 months ago
I am trying to deploy a container from a private gcp artifact repository, but it's stuck at creating containers for 15+ minutes.
If I reload the page, the single service is rendered in a loading state, with a github octocat.
I know my container won't start without a config provided, but I could see nothing in logs.
Another annoyance during creation is that pasting the private docker image in, didn't do anything. I was merely given a link to the google page. I had to create a hello-world docker image deployment, edit settings, apply credentials, and then change the image to the private registry.
13 Replies
Now, about 30 minutes later, it's still stuck like this for me.
Attachments
I finally got the UI to give me some logs, but the service is still rendered in a loading state
Attachments
If I click back on the service, I end up with an endless spinner as well. I can only get to the deploy log view, via the notification I got, when the deploy failed.
2 months ago
Same as me, stuck at creating containers
error:
Error: Failed to read app source directoryCaused by: No such file or directory (os error 2)nixpacks exited with an error
What happened:
>eployment got stuck at “Creating containers”.
> aborted/removed that stuck deployment.
> since then, every new deployment for this API service only fails at image build with the same error.
2 months ago
I think that issue is unrelated, as I am trying to deploy an existing docker image, not trying to build anything.
Looking at my deployment settings, it seems like the username is encrypted, but the password field is plaintext.
Could that be why the UI is broken, as it expects an encrypted value for the password field as well?
I've now created a new project, and added credentials to a public image. Both fields are encrypted.
While creating my original project in the UI, I wrote the full project name, and noticed it missed the last character in the name after it was saved.
Could this be due to state changes not being propagated before the save is triggered?
Whenever I try the combination of _json_key and the json service account, it's not encrypting the password for the registryCredentials for some reason.
Okay, so I've changed the username to _json_key_base64 and used a base64 encoded version of the service account json file.
According to google docs: https://docs.cloud.google.com/artifact-registry/docs/docker/authentication#json-key
The problem is your encryption is disabled for json string content in the UI, you should probably fix that either in the docs, or in the UI.
I've finally managed to get my new project further, so I'll rename the old one so you can debug on your end if you need more details.
2 months ago
Any updates on the private registry issue?
2 months ago
Hey, we pushed a fix for this, and your project should no longer be stuck in a loading state.