Can I build the server image myself and push it to our own registry?

Example threads. These questions and answers were written by the SDODS team to document real problems and how to fix them. The people named are illustrative, not real users. Questions asked on this site are marked new.

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?

install docker ci

asked by Zeynep Arslan

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.
bash
```
docker build -t sdods-server .
docker run --rm sdods-server doctor
```
Tag it for your registry and push it like anything else. The entrypoint behaves identically no matter where the image is stored — serve by default, bootstrap, and any other argument goes to the CLI.
answered by Nikhil Sane
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 doctor is 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 OyelaranSDODS team

Know the answer?

Wrap commands and output in triple backticks and they will render as a code block.

Checking whether you’re signed in…

Have a different question? Ask it.

Can I build the server image myself and push it to our own registry?

2 answers

Know the answer?

Related