(HTTP code 500) server error - invalid reference format
-
wrote 25 days ago last edited by
How can I debug this error?
(HTTP code 500) server error - invalid reference format
The image successfully builds locally.
-
How can I debug this error?
(HTTP code 500) server error - invalid reference format
The image successfully builds locally.
@ekevu123 said in (HTTP code 500) server error - invalid reference format:
invalid reference format
This usually means something is wrong with the docker image name. What is the context for this error though?
-
wrote 25 days ago last edited by ekevu123 25 days ago
Well, there was no context. It uploads the source tarball, gives it a build ID, and then this error happens.
-
Well, there was no context. It uploads the source tarball, gives it a build ID, and then this error happens.
-
wrote 25 days ago last edited by
The first line is "using build service" and then the link.
The second line is "Building" followed by the repository name and the image tag.
Then it says "uploading source tarball"
Then it has a BuildID
and then the error comes -
The first line is "using build service" and then the link.
The second line is "Building" followed by the repository name and the image tag.
Then it says "uploading source tarball"
Then it has a BuildID
and then the error comes@ekevu123 said in (HTTP code 500) server error - invalid reference format:
The second line is "Building" followed by the repository name and the image tag.
yes, here it seems there is something wrong with the name and image tag. I am not sure how to test for the validity of this (maybe chatgpt?) . But maybe you can see docker tag works locally (on some random test image)?
-
wrote 23 days ago last edited by
But how would I even be able to influence this? I think a recent change has caused that I can only run cloudron build and it doesn't take any arguments anymore? I think that behaviour used to be different. So, what else could I theoretically do except running cloudron build?
-
wrote 23 days ago last edited by
True, it seems like the only things I can do are log out and log back in, and set the repository.
I am still unsure why it doesn't work for this one repository while it does work using docker build. I am happy to investigate this myself, but what is the difference between the two services exactly, except that one works on the server and the other locally? If I understood that, I would be happy to investigate. -
docker build is building the image locally. cloudron build is pretty much doing the same thing but on a remote server. The code is at https://git.cloudron.io/packages/docker-builder-app/ . There is no difference other than what you already said.