Skip to content

test(e2e): bump compose-bridge images to v0.0.7 - #14170

Merged
glours merged 2 commits into
docker:mainfrom
ricardobranco777:fix_version_007
Sep 2, 2026
Merged

test(e2e): bump compose-bridge images to v0.0.7#14170
glours merged 2 commits into
docker:mainfrom
ricardobranco777:fix_version_007

Conversation

@ricardobranco777

Copy link
Copy Markdown
Contributor

What I did

v0.0.3 had a mis-published multi-arch manifest, causing exec format errors on non-amd64 architectures.

Fixed upstream in docker/compose-bridge-transformer@665f67e.

Otherwise test fails on openQA: https://openqa.opensuse.org/tests/6193496#external

# Test messages # TestConvertBuildOnlyService
# failure: 

Failed
=== RUN   TestConvertBuildOnlyService
=== PAUSE TestConvertBuildOnlyService
=== CONT  TestConvertBuildOnlyService
    framework.go:170: WARNING: docker-model cli-plugin not found
    bridge_test.go:66: Running command: docker compose version
    bridge_test.go:69: Running command: docker compose -f ./fixtures/bridge-build-only/compose.yaml --project-name bridge-build-only bridge convert --output /tmp/TestConvertBuildOnlyService2914424688/003 --transformation docker/compose-bridge-kubernetes:v0.0.3
v0.0.3: Pulling from docker/compose-bridge-kubernetes
    bridge_test.go:69: assertion failed: 
        Command:  docker compose -f ./fixtures/bridge-build-only/compose.yaml --project-name bridge-build-only bridge convert --output /tmp/TestConvertBuildOnlyService2914424688/003 --transformation docker/compose-bridge-kubernetes:v0.0.3
        ExitCode: 255
        Error:    exit status 255
        Stdout:   v0.0.3: Pulling from docker/compose-bridge-kubernetes
        b1b15940657b: Pulling fs layer
        4e3b1e361818: Pulling fs layer
        6bd31a75b555: Download complete
        13d5fb902dea: Download complete
        b1b15940657b: Download complete
        4e3b1e361818: Download complete
        b1b15940657b: Pull complete
        4e3b1e361818: Pull complete
        Digest: sha256:4ffd3f23f377b1fdd9d0195732980e7534a8975c8a210a12681dc803c002f761
        Status: Downloaded newer image for docker/compose-bridge-kubernetes:v0.0.3
        
        Stderr:   time="2026-08-30T08:13:55-04:00" level=warning msg="image bridge-build-only-app for service app not found locally; Dockerfile-exposed ports will not be included — run `docker compose build` first to include them"
        exec /transform: exec format error
        
        
        
        Failures:
        ExitCode was 255 expected 0
        Expected no error
    framework.go:143: Contents of config dir:
    framework.go:145:   - /tmp/TestConvertBuildOnlyService2914424688/001
    framework.go:145:   - /tmp/TestConvertBuildOnlyService2914424688/001/cli-plugins
    framework.go:145:   - /tmp/TestConvertBuildOnlyService2914424688/001/cli-plugins/docker-buildx
    framework.go:145:   - /tmp/TestConvertBuildOnlyService2914424688/001/cli-plugins/docker-compose
    framework.go:145:   - /tmp/TestConvertBuildOnlyService2914424688/001/cli-plugins/docker-scan
--- FAIL: TestConvertBuildOnlyService (2.95s)

Related issue

(not mandatory) A picture of a cute animal, if possible in relation to what you did

v0.0.3 had a mis-published multi-arch manifest, causing exec format
errors on non-amd64 architectures.

Fixed upstream in docker/compose-bridge-transformer@665f67e.

Signed-off-by: Ricardo Branco <rbranco@suse.de>
glours
glours previously approved these changes Sep 2, 2026

@glours glours left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you @ricardobranco777 🙏

@glours

glours commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

Root cause

The TestConvertAndTransformList/kubernetes_manifests and /helm_charts failures aren't caused by anything in this PR's diff — they're caused by an intentional behavior change upstream in compose-bridge-transformer between v0.0.3 and v0.0.7, not reflected in this repo's e2e fixtures.

Commit 7f56eaa ("Remove egress restriction from generated NetworkPolicy", PR #17, shipped starting in v0.0.6) deliberately drops the Egress policy type and the accompanying egress block from the generated NetworkPolicy manifests — it was blocking DNS resolution (CoreDNS) and other legitimate outbound traffic, since Compose's network model only restricts ingress between services, not egress.

Bumping bridgeImageVersion to v0.0.7 in pkg/e2e/bridge_test.go is correct, but the 4 checked-in expected fixtures below still contain the old (now removed) egress restriction, so diff -r against the freshly generated output fails.

Files to update

  • pkg/e2e/fixtures/bridge/expected-kubernetes/base/private-network-network-policy.yaml
  • pkg/e2e/fixtures/bridge/expected-kubernetes/base/public-network-network-policy.yaml
  • pkg/e2e/fixtures/bridge/expected-helm/templates/private-network-network-policy.yaml
  • pkg/e2e/fixtures/bridge/expected-helm/templates/public-network-network-policy.yaml

Diff

--- a/pkg/e2e/fixtures/bridge/expected-kubernetes/base/private-network-network-policy.yaml
+++ b/pkg/e2e/fixtures/bridge/expected-kubernetes/base/private-network-network-policy.yaml
@@ -11,14 +11,8 @@
             com.docker.compose.network.private-network: "true"
     policyTypes:
         - Ingress
-        - Egress
     ingress:
         - from:
             - podSelector:
                 matchLabels:
                     com.docker.compose.network.private-network: "true"
-    egress:
-        - to:
-            - podSelector:
-                matchLabels:
-                    com.docker.compose.network.private-network: "true"
--- a/pkg/e2e/fixtures/bridge/expected-kubernetes/base/public-network-network-policy.yaml
+++ b/pkg/e2e/fixtures/bridge/expected-kubernetes/base/public-network-network-policy.yaml
@@ -11,14 +11,8 @@
             com.docker.compose.network.public-network: "true"
     policyTypes:
         - Ingress
-        - Egress
     ingress:
         - from:
             - podSelector:
                 matchLabels:
                     com.docker.compose.network.public-network: "true"
-    egress:
-        - to:
-            - podSelector:
-                matchLabels:
-                    com.docker.compose.network.public-network: "true"
--- a/pkg/e2e/fixtures/bridge/expected-helm/templates/private-network-network-policy.yaml
+++ b/pkg/e2e/fixtures/bridge/expected-helm/templates/private-network-network-policy.yaml
@@ -11,14 +11,8 @@
             com.docker.compose.network.private-network: "true"
     policyTypes:
         - Ingress
-        - Egress
     ingress:
         - from:
             - podSelector:
                 matchLabels:
                     com.docker.compose.network.private-network: "true"
-    egress:
-        - to:
-            - podSelector:
-                matchLabels:
-                    com.docker.compose.network.private-network: "true"
--- a/pkg/e2e/fixtures/bridge/expected-helm/templates/public-network-network-policy.yaml
+++ b/pkg/e2e/fixtures/bridge/expected-helm/templates/public-network-network-policy.yaml
@@ -11,14 +11,8 @@
             com.docker.compose.network.public-network: "true"
     policyTypes:
         - Ingress
-        - Egress
     ingress:
         - from:
             - podSelector:
                 matchLabels:
                     com.docker.compose.network.public-network: "true"
-    egress:
-        - to:
-            - podSelector:
-                matchLabels:
-                    com.docker.compose.network.public-network: "true"

v0.0.6 dropped the Egress policyType/block from generated
NetworkPolicy manifests since it blocked CoreDNS traffic; update
the fixtures to match.

Signed-off-by: Ricardo Branco <rbranco@suse.de>
auto-merge was automatically disabled September 2, 2026 15:20

Head branch was pushed to by a user without write access

@ricardobranco777

Copy link
Copy Markdown
Contributor Author

Root cause

Yup. This solved it.

@glours
glours enabled auto-merge (rebase) September 2, 2026 16:13
@glours
glours disabled auto-merge September 2, 2026 16:21
@glours
glours merged commit 4121ec7 into docker:main Sep 2, 2026
90 of 115 checks passed
@codecov

codecov Bot commented Sep 2, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@ricardobranco777
ricardobranco777 deleted the fix_version_007 branch September 2, 2026 16:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants