Docker buildx build from pomerium image with --platform linux/amd64

Support
1

I try to build a customized pomerium image.
In the Dockerfile, I base the image on
FROM cr.pomerium.com/pomerium/pomerium:latest

Build succeeds on for linux/arm64/v8.
Build fails for --platform linux/amd64 on local machine and in Google Cloud:

...

Step #5: ERROR: failed to solve: cr.pomerium.com/pomerium/pomerium:latest: failed to resolve source metadata for cr.pomerium.com/pomerium/pomerium:latest: failed to copy: httpReadSeeker: failed open: unexpected status code https://cr.pomerium.com/v2/pomerium/pomerium/manifests/sha256:7de64951ac92f7967c6d7229a687082d519ec908d224c18c5650e13891e34e45: 500 Internal Server Error - Server message: unknown: unknown error
Finished Step #5
ERROR
ERROR: build step 5 "gcr.io/cloud-builders/docker" failed: step exited with non-zero status: 1

Seems it is trying to resolve
https://cr.pomerium.com/v2/pomerium/pomerium/manifests/sha256:7de64951ac92f7967c6d7229a687082d519ec908d224c18c5650e13891e34e45, which yields

{"errors":[{"code":"UNKNOWN","message":"unknown error","detail":{"Op":"Get","URL":"https://registry-1.docker.io/v2/pomerium/pomerium/manifests/sha256:7de64951ac92f7967c6d7229a687082d519ec908d224c18c5650e13891e34e45","Err":{"code":"TOOMANYREQUESTS","message":"Too Many Requests (HAP429).\n"}}}]}

when opened in the browser.

Is linux/amd64 not available possibly?

2

changing to FROM pomerium/pomerium:latest fixed it.

1 Like
3

Hi ogreyard,

Great to hear you’ve been getting Pomerium working for you!

It sounds like you’re a power user - would you like to access Pomerium Zero beta? Would a web-based console for managing Pomerium be useful for you?