Open jclsn opened 1 year ago
How did you create the image you are trying to pull (e.g. build it with a Dockerfile, mirrored the upstream pyrex image)? It looks like the image might be malformed from what pyrex is expecting (e.g. it's missing the capture script)
I would have to research as I am not the creator of the image.Am 12.01.2023 um 17:18 schrieb Joshua Watt @.***>: How did you create the image you are trying to pull (e.g. build it with a Dockerfile, mirrored the upstream pyrex image)? It looks like the image might be malformed from what pyrex is expecting (e.g. it's missing the capture script)
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>
Pyrex has some very specific requirements for what's in the image (see the contents of the image directory), so you can't just use "any" image with it. If you want a custom image, I would recommend starting with one of the base Pyrex images, or at least looking into the image requirement by reading through the Dockerfile.
I can't seem to get the syntax right for this. I get the following output, when I run
docker images
I am trying to edit the
pyrex.ini
as followsbut I am getting the following output
I am assuming the whole url is not assembled correctly. Is there any way I can get Pyrex to provide verbose output to see what it actually tries to pull from?
EDIT: Okay, I just edited the
pyrex.ini
and printed thetag
variable, which seems to be assembled correctly with the registry. No idea why it is failing. Could it be the port? The registry also requires a login. Does Pyrex support that?