You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
quarkus dev tools like testcontainers don't seems compatible with podman
On fedora, with podman and podman-docker packages, we have errors like :
2021-10-01 16:11:59,612 ERROR [org.tes.doc.DockerClientProviderStrategy] (build-19) Could not find a valid Docker environment. Please check configuration. Attempted configurations were:
2021-10-01 16:11:59,612 ERROR [org.tes.doc.DockerClientProviderStrategy] (build-19) EnvironmentAndSystemPropertyClientProviderStrategy: failed with exception TimeoutException (Timeout waiting for result with exception). Root cause LastErrorException ([13] Permission non accordée)
2021-10-01 16:11:59,613 ERROR [org.tes.doc.DockerClientProviderStrategy] (build-19) UnixSocketClientProviderStrategy: failed with exception InvalidConfigurationException (Could not find unix domain socket). Root cause AccessDeniedException (/var/run/docker.sock)
2021-10-01 16:11:59,614 ERROR [org.tes.doc.DockerClientProviderStrategy] (build-19) As no valid configuration was found, execution cannot continue
2021-10-01 16:11:59,621 ERROR [io.qua.dep.dev.IsolatedDevModeMain] (main) Failed to start quarkus: java.lang.RuntimeException: io.quarkus.builder.BuildException: Build failure: Build failed due to errors
[error]: Build step io.quarkus.oidc.deployment.devservices.keycloak.KeycloakDevServicesProcessor#startKeycloakContainer threw an exception: java.lang.IllegalStateException: Could not find a valid Docker environment. Please see logs and check configuration
quarkus dev tools like testcontainers don't seems compatible with podman
On fedora, with podman and podman-docker packages, we have errors like :
Issue found on testcontainers to indicate they wait podman team : testcontainers/testcontainers-go#336
But no issue found on podman or in quarkus... Work in progress ?
The text was updated successfully, but these errors were encountered: