[Feature]: Apple container

[halotukozak]

Module

None

Problem

Support Apple containerisation
https://github.com/apple/container

Solution

Add alternative to docker on MacOS

Benefit

more lightweight containerisation optimised for Apple silicon

Alternatives

abandon this idea

Would you like to help contributing this feature?

Yes

[eddumelendez]

It doesn't expose a docker compatible API. See apple/container#66

[alvarosanchez]

It kinda works with socktainer.

Ryuk doesn't seem to work, but disabling it made TC and Apple containers working for me:

[test-resources-service] 15:16:25.395 [pool-1-thread-1] INFO  o.testcontainers.DockerClientFactory - Testcontainers version: 2.7.3
[test-resources-service] 15:16:25.610 [pool-1-thread-1] INFO  o.t.d.DockerClientProviderStrategy - Found Docker environment with Testcontainers Host with tc.host=tcp://127.0.0.1:49325
[test-resources-service] 15:16:25.610 [pool-1-thread-1] INFO  o.testcontainers.DockerClientFactory - Docker host IP address is 127.0.0.1
[test-resources-service] 15:16:25.616 [pool-1-thread-1] INFO  o.testcontainers.DockerClientFactory - Connected to docker: 
  Server Version: container-apiserver version 0.6.0 (build: release, commit: a23bcf0) (via Testcontainers Desktop 1.15.1)
  API Version: v1.51
  Operating System: 
  Total Memory: 32768 MB
[test-resources-service] 15:16:25.617 [pool-1-thread-1] WARN  o.t.utility.ResourceReaper - 
********************************************************************************
Ryuk has been disabled. This can cause unexpected behavior in your environment.
********************************************************************************
[test-resources-service] 15:16:25.618 [pool-1-thread-1] INFO  o.testcontainers.DockerClientFactory - Checking the system...
[test-resources-service] 15:16:25.619 [pool-1-thread-1] INFO  o.testcontainers.DockerClientFactory - ✔︎ Docker server version should be at least 1.6.0
[test-resources-service] 15:16:27.458 [virtual-executor6] INFO  tc.postgres:latest - Creating container for image: postgres:latest
[test-resources-service] 15:16:27.610 [virtual-executor6] INFO  tc.postgres:latest - Container postgres:latest is starting: c347102e-e236-4fa9-a0ee-e8d0f38a3228
[test-resources-service] 15:16:28.550 [virtual-executor6] WARN  tc.postgres:latest - The architecture 'null' for image 'postgres:latest' (ID docker.io/library/postgres:latest) does not match the Docker server architecture 'arm64'. This will cause the container to execute much more slowly due to emulation and may lead to timeout failures.
[test-resources-service] 15:16:29.287 [virtual-executor6] INFO  tc.postgres:latest - Container postgres:latest started in PT1.653009S
[test-resources-service] 15:16:29.288 [virtual-executor6] INFO  tc.postgres:latest - Container is started (JDBC URL: jdbc:postgresql://127.0.0.1:53700/test?loggerLevel=OFF)

This is something to be aware of:

[WARN  tc.postgres:latest - The architecture 'null' for image 'postgres:latest' (ID docker.io/library/postgres:latest) does not match the Docker server architecture 'arm64'. This will cause the container to execute much more slowly due to emulation and may lead to timeout failures.

Which indeed makes Postgres ~500ms slower than e.g. TC's embedded runtime