chore(camel-test-infra-iggy): upgrade iggy.container to 0.8.0

[github-actions]

This PR updates the iggy.container container image to version 0.8.0.

Update Details

• Property: iggy.container
• Image: mirror.gcr.io/apache/iggy
• File: /home/runner/work/camel/camel/test-infra/camel-test-infra-iggy/src/main/resources/org/apache/camel/test/infra/iggy/services/container.properties
• Old version: 0.7.0
• New version: 0.8.0

Verification

Please verify:

• Container image version is compatible with existing tests
• No breaking changes in the updated version
• Tests pass with the new version

Run the following to rebuild the test infra:

mvn clean verify -pl camel-test-infra-iggy

Then test the impacted components.

---

This PR was automatically created by the Container Version Upgrade workflow.

[apupier]

test failing fo rme locally:

2026-06-08T09:02:12.762392252Z main ERROR Could not start container
java.lang.IllegalStateException: Wait strategy failed. Container exited with code 101
	at org.testcontainers.containers.GenericContainer.tryStart(GenericContainer.java:520)
	at org.testcontainers.containers.GenericContainer.lambda$doStart$0(GenericContainer.java:341)
	at org.rnorth.ducttape.unreliables.Unreliables.retryUntilSuccess(Unreliables.java:81)
	at org.testcontainers.containers.GenericContainer.doStart(GenericContainer.java:331)
	at org.testcontainers.containers.GenericContainer.start(GenericContainer.java:317)
	at org.apache.camel.test.infra.iggy.services.IggyLocalContainerInfraService.initialize(IggyLocalContainerInfraService.java:57)

=== io_uring Permission Denied ===

The io_uring runtime requires specific syscalls that are blocked by default
in containerized environments (Docker, Podman, etc.).

To resolve this issue:

  1. Docker Compose (add to service):
     security_opt:
       - seccomp:unconfined

  2. Docker run:
     docker run --security-opt seccomp=unconfined ...

  3. Custom seccomp profile (more secure):
     Create a profile allowing io_uring_setup, io_uring_enter,
     and io_uring_register syscalls.

  4. Kubernetes (add to pod spec):
     securityContext:
       seccompProfile:
         type: Unconfined

  Need help? Join our Discord: https://discord.gg/apache-iggy


thread 'main' (1) panicked at core/server/src/main.rs:121:13:
Cannot create runtime: Permission denied (os error 13)
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

[oscerd]

Thanks for the bump. Flagging a blocker that @apupier already documented: the iggy 0.8.0 image fails to start under the default container seccomp profile — its new io_uring-based runtime hits denied syscalls and the server panics (Cannot create runtime: Permission denied (os error 13), exit 101). So this isn't an arch-availability issue (mirror.gcr.io/apache/iggy:0.8.0 does exist); it's a runtime regression.

The fix belongs in the test-infra service (IggyLocalContainerInfraService) — e.g. running the container with seccomp=unconfined (or allow-listing the io_uring_* syscalls) — rather than in the version string alone. Could you fold that in here, or split the infra change out first? The version-bump diff itself is clean.

---

Reviewed with Claude Code on behalf of Andrea Cosentino. This review was generated by an AI agent and may contain inaccuracies; please verify all suggestions before applying.