How to properly use a custom image from another registry?

[jclsn]

I can't seem to get the syntax right for this. I get the following output, when I run docker images

git.custom.com:1234/some-path/some-path/someimage   latest    2848f820ea3   3 months ago   631MB

I am trying to edit the pyrex.ini as follows

tag = some-path/some-path/someimage:latest

registry = git.custom.com

but I am getting the following output

docker: Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "/usr/libexec/pyrex/capture": stat /usr/libexec/pyrex/capture: no such file or directory: unknown.

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 the tag 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?

[JoshuaWatt]

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)

[jclsn]

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: ***@***.***>

[JoshuaWatt]

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.