fix(ci): docker build met --network=host tegen hangende registry-stappen
De host heeft Docker iptables uitgeschakeld, dus build-containers op bridge hebben geen outbound internet; 'npm install -g pnpm' in de builder-stage hing daardoor. Met --network=host krijgt de build wel registry-toegang. Contract-test vergrendelt de flag.
This commit is contained in:
1 parent
cdb0fef6c9
commit
43ecdaee19
2 files changed
+8
No files matched your search
@@ -65,7 +65,11 @@ jobs:
|
||||
|
||||
- name: Build image
|
||||
run: |
|
||||
# --network=host is vereist: deze host heeft Docker iptables
|
||||
# uitgeschakeld, dus build-containers op het bridge-netwerk
|
||||
# hebben geen outbound internet (npm/pnpm zouden hangen).
|
||||
DOCKER_BUILDKIT=1 docker build \
|
||||
--network=host \
|
||||
--build-arg NODE_OPTIONS="--max-old-space-size=1536" \
|
||||
--cache-from epicnext-cms:latest \
|
||||
-t epicnext-cms:latest .
|
||||
|
||||
@@ -24,6 +24,10 @@ describe("deploy job", () => {
|
||||
expect(deployJob).toContain("-t epicnext-cms:latest");
|
||||
});
|
||||
|
||||
it("builds on host network for registry access", () => {
|
||||
expect(deployJob).toContain("--network=host");
|
||||
});
|
||||
|
||||
it("stops old container before starting new one", () => {
|
||||
expect(deployJob).toContain("docker stop epicnext-cms-app");
|
||||
expect(deployJob).toContain("docker rm epicnext-cms-app");
|
||||
|
||||
Reference in new issue
Block a user