Our cluster only pulls from an internal registry, so pulling from a public one is not an option regardless of how convenient it is. Is building the image ourselves supported, or is the published one the only route?
asked by Zeynep Arslan64 ·
Can I build the server image myself and push it to our own registry?
Asked 640 views2 answers
2 answers
Supported — the image is built from a Dockerfile in the checkout, on the official Playwright base, so the browser engines come in with the base rather than being downloaded during the build.
bashdocker build -t sdods-server . docker run --rm sdods-server doctorTag it for your registry and push it like anything else. The entrypoint behaves identically no matter where the image is stored —
serveby default,bootstrap, and any other argument goes to the CLI.answered by Nikhil Sane487 ·If you build for a mix of hardware, be deliberate about it: building an arm64 image under emulation on an amd64 runner is very slow, for the same reason the published image is amd64 only. A native runner per architecture is the difference between minutes and not finishing.
docker run --rm sdods-server doctoris the right smoke test for the built image, and it is worth running in the build pipeline rather than after the push.answered by Daniel Oyelaranmaintainer24,177 ·
Have the same question?
Ask it with the command you ran and the output you got, and it will be answered here.
Ask a questionRelated
- Installing onto a machine with no outbound internet at all0 answers
- Linting only the staged feature files in a pre-commit hook — is --json stable enough?0 answers
- Unsupported architecture: i686 — is 32-bit Linux out entirely?0 answers
- NO_PUBKEY on apt update even though I installed the SDODS key3 answers
- apt update: the repository "does not have a Release file"4 answers