The image is described as the server and the web UI. Our CI does not need a UI, it needs to run the API layer and fail the build. Is the image the wrong tool for that, or does it do both?
asked by Bruno Teixeira694 ·
Can I run a suite with the Docker image, or is it only the server?
Asked 2,470 views3 answers
3 answers
Accepted answer
It does both. The entrypoint defaults to
serve, understandsbootstrap, and passes anything else straight to the CLI. So any command you would run locally is an argument to the container:bashdocker run --rm ghcr.io/siri1410/sdods-server run -p demo-shop -e staging -l apiThe exit code comes back through, which is the part that matters for a build gate.
For a UI layer you need nothing extra — the browser engines are already inside the image. That is the one channel that needs nothing at all installed on the host.
answered by Nikhil Sane487 ·Mount your project in and point the run at it, or it will only ever see the demo project that ships inside the image:
bashdocker run --rm -v "$PWD":/work -w /work ghcr.io/siri1410/sdods-server run -p my-app -e staging -l apiProjects are discovered from the working directory, so
-wis doing real work in that line and not just tidiness.answered by Priya Venkateshmaintainer29,604 ·On Apple silicon add
--platform linux/amd64to both of those — the image is amd64 only and Docker refuses the pull rather than emulating on its own.answered by Lars Vinter276 ·
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