ci(cd): build multi-arch images (amd64 + arm64) - #64
Merged
Merged
Conversation
torridfish
marked this pull request as draft
July 16, 2026 08:51
torridfish
added a commit
that referenced
this pull request
Jul 16, 2026
Build the image on PRs (no push) so a broken Dockerfile — the pyopenjtalk compile and the open_jtalk_dic / UniDic bake layers that make the runtime self-contained — fails the PR instead of the release build. A --network none smoke test runs the in-process OpenJTalk frontend to confirm the baked dictionaries resolve offline. amd64 only; arm64 PR gating is left to the multi-arch work in #64.
torridfish
added a commit
that referenced
this pull request
Jul 16, 2026
Build the image on PRs (no push) so a broken Dockerfile — the pyopenjtalk compile and the open_jtalk_dic / UniDic bake layers that make the runtime self-contained — fails the PR instead of the release build. A --network none smoke test runs the in-process OpenJTalk frontend to confirm the baked dictionaries resolve offline. amd64 only; arm64 PR gating is left to the multi-arch work in #64.
torridfish
changed the base branch from
main
to
feat/commercializable-openjtalk
September 13, 2026 12:27
torridfish
force-pushed
the
ci/multi-arch-images
branch
from
September 13, 2026 12:36
f4e07a9 to
f8d8927
Compare
torridfish
added a commit
to sessatakuma/jpcorrect-backend
that referenced
this pull request
Sep 13, 2026
#38 added runtime hardening to the backend service in compose.deploy.yml (read_only + tmpfs /tmp + no-new-privileges). This stack replaces that file, so re-apply it and extend it to everything the stack runs: - backend-dev gets the same three keys as backend-prod. Dev skips the app-level auth middlewares, so the container-level guarantees matter more there. - api-tools-prod / api-tools-dev get them too. Verified on the arm64 deploy host: a read-only api-tools container serves /docs and a real MarkAccent request, so the bundled OpenJTalk/UniDic dicts need nothing writable but /tmp. - postgres-{prod,dev} keep a writable rootfs (initdb + PGDATA) but get no-new-privileges; verified the entrypoint's drop to the postgres user still works under it. - cloudflared gets no-new-privileges, and both watchtowers get the full set. - cloudflared and watchtower are pinned to explicit versions instead of :latest. Watchtower holds the Docker socket, which makes it the last thing that should float; 1.7.1 is verified working on the deploy host. Also turn auto-update off for api-tools only. Watchtower stays scope-split per env, but both api-tools services now carry watchtower.enable=false: the backend publishes multi-arch images since #38, while API-tools is still amd64-only, so a pull on the arm64 host would replace a working image with an unrunnable one. Blocked on sessatakuma/API-tools#64; the runbook documents how to flip it back. Finally, keep publishing :latest alongside :dev on the default branch so the conventional tag can't silently go stale. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
torridfish
added a commit
to sessatakuma/jpcorrect-backend
that referenced
this pull request
Sep 13, 2026
#38 added runtime hardening to the backend service in compose.deploy.yml (read_only + tmpfs /tmp + no-new-privileges). This stack replaces that file, so re-apply it and extend it to everything the stack runs: - backend-dev gets the same three keys as backend-prod. Dev skips the app-level auth middlewares, so the container-level guarantees matter more there. - api-tools-prod / api-tools-dev get them too. Verified on the arm64 deploy host: a read-only api-tools container serves /docs and a real MarkAccent request, so the bundled OpenJTalk/UniDic dicts need nothing writable but /tmp. - postgres-{prod,dev} keep a writable rootfs (initdb + PGDATA) but get no-new-privileges; verified the entrypoint's drop to the postgres user still works under it. - cloudflared gets no-new-privileges, and both watchtowers get the full set. - cloudflared and watchtower are pinned to explicit versions instead of :latest. Watchtower holds the Docker socket, which makes it the last thing that should float; 1.7.1 is verified working on the deploy host. Also turn auto-update off for api-tools only. Watchtower stays scope-split per env, but both api-tools services now carry watchtower.enable=false: the backend publishes multi-arch images since #38, while API-tools is still amd64-only, so a pull on the arm64 host would replace a working image with an unrunnable one. Blocked on sessatakuma/API-tools#64; the runbook documents how to flip it back. Finally, keep publishing :latest alongside :dev on the default branch so the conventional tag can't silently go stale. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
torridfish
added this pull request to stack #66
September 13, 2026 12:44
torridfish
force-pushed
the
ci/multi-arch-images
branch
from
September 13, 2026 14:50
f8d8927 to
f028216
Compare
🛡️ PR Quality Check Summary✅ PR Title: Passed (Length: 47/75, Format: OK). 🎉 All checks passed! |
torridfish
marked this pull request as ready for review
September 13, 2026 14:54
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
wade00754
approved these changes
Sep 14, 2026
This was referenced Sep 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
目的
Publish arm64 images alongside amd64 so the service runs natively on the arm64 (Oracle Ampere) deploy host. Images are amd64-only today.
方法／實作說明
Add
linux/arm64to the build-pushplatformsin the CD workflow. QEMU and Buildx are already configured, so the published tags (:stable/:dev/ semver /sha-*) become multi-arch manifest lists..github/workflows/cd.ymldocker/build-push-action(provenance/sbomunchanged).關聯 Issue
Closes #65.
附註