Keycloak DevService not starting on enabled project

[InfoSec812]

I have the following dependencies installed:

    <dependency>
      <groupId>io.quarkus</groupId>
      <artifactId>quarkus-oidc</artifactId>
    </dependency>
    <dependency>
      <groupId>io.quarkus</groupId>
      <artifactId>quarkus-keycloak-authorization</artifactId>
    </dependency>

I have the following configuration:

"%localdev":
  quarkus:
    quinoa:
      enable-spa-routing: true
      dev-server:
        port: 3000
      package-manager-command:
        build: npm run build:quinoa
    oidc:
      application-type: web-app
      discovery-enabled: false
      authorization-path: /protocol/openid-connect/auth
      # Token endpoint: http://localhost:8180/realms/quarkus/protocol/openid-connect/token
      token-path: /protocol/openid-connect/token
      # JWK set endpoint: http://localhost:8180/realms/quarkus/protocol/openid-connect/certs
      jwks-path: /protocol/openid-connect/certs
      # UserInfo endpoint: http://localhost:8180/realms/quarkus/protocol/openid-connect/userinfo
      user-info-path: /protocol/openid-connect/userinfo
      # Token Introspection endpoint: http://localhost:8180/realms/quarkus/protocol/openid-connect/tokens/introspect
      introspection-path: /protocol/openid-connect/tokens/introspect
    keycloak:
      devservices:
        realm-path: ${PWD}
        enabled: true

When I start my application in dev mode:

./mvnw clean compile quarkus:dev -Dquarkus.profile=localdev

My PostgreSQL container for the application starts and my liquibase migrations happen and my quinoa webapp get's proxied correctly, BUT the Keycloak container does not get started??

I see no errors related to the start of the containers and I see no indication that it ever tried to even pull the container image.

Any suggestions would be greatly appreciated!

Cheers,

FYI: Vital details:

OS: MacOS 12.5.1
Podman: 4.2.1
Quarkus Version: 2.12.2.Final

[quarkus-bot[bot]]

/cc @pedroigor, @sberyozkin

[InfoSec812]

Aha! I missed a configuration required... In my default quarkus configuration I had auth-server-url defined which is documented to disable the keycloak devservices! Removing that setting from the default configuration allowed the keycloak container to start!

[sberyozkin]

@InfoSec812 Great, FYI, the realm path should point to a specific realm file not a directory - the reason it still starts is that in this case a default quarkus realm is created

[sberyozkin]

@InfoSec812 You can also prepend quarkus.oidc.auth-server-url with %prod..
And you can also access the already running Keycloak from Dev UI if quarkus.oidc.auth-server-url is configured

[dscoppelletti]

I have the same problem.

I followed the guide https://quarkus.io/guides/security-openid-connect, so my application.properties is:

%prod.quarkus.oidc.auth-server-url=http://localhost:8180/realms/quarkus
quarkus.oidc.client-id=backend-service
quarkus.oidc.credentials.secret=secret
quarkus.keycloak.devservices.realm-path=/Users/dario/github/dscoppelletti/quarkus-guides/security-openid-connect-quickstart/config/quarkus-realm.json

auth-server-url should be ignored by quarkus dev because is prefixed by %prod.

realm-path points to the absolute path of quarkus-realm.json because I don't understand where I must to put the file.

Can someone help me?
Thanks

[dscoppelletti]

I use Quarkus 2.13.3 and Docker Desktop 4.13.0.
When I run quarkus dev, Docker should be running or not?
Maybe this is a silly question, but, if Docker is running, I get:

2022-10-27 18:07:29,626 WARN  [org.tes.uti.TestcontainersConfiguration] (build-25) Attempted to read Testcontainers configuration file at file:/Users/dario/.testcontainers.properties but the file was not found. Exception message: FileNotFoundException: /Users/dario/.testcontainers.properties (No such file or directory)
2022-10-27 18:07:29,653 INFO  [org.tes.doc.DockerMachineClientProviderStrategy] (build-25) docker-machine executable was not found on PATH ([/Users/dario/projects/sdkman/candidates/springboot/current/bin, /Users/dario/projects/sdkman/candidates/quarkus/current/bin, /Users/dario/projects/sdkman/candidates/java/current/bin, /Users/dario/Library/Android/sdk/platform-tools, /Users/dario/Library/Android/sdk/tools/bin, /Users/dario/Library/Android/sdk/tools, /Users/dario/bin, /usr/local/bin, /System/Cryptexes/App/usr/bin, /usr/bin, /bin, /usr/sbin, /sbin, /usr/local/go/bin, /Library/Apple/usr/bin])
2022-10-27 18:07:29,655 ERROR [org.tes.doc.DockerClientProviderStrategy] (build-25) Could not find a valid Docker environment. Please check configuration. Attempted configurations were:
2022-10-27 18:07:29,657 ERROR [org.tes.doc.DockerClientProviderStrategy] (build-25)     UnixSocketClientProviderStrategy: failed with exception InvalidConfigurationException (Could not find unix domain socket). Root cause NoSuchFileException (/var/run/docker.sock)
2022-10-27 18:07:29,658 ERROR [org.tes.doc.DockerClientProviderStrategy] (build-25) As no valid configuration was found, execution cannot continue
2022-10-27 18:07:29,626 WARN  [org.tes.uti.TestcontainersConfiguration] (build-25) Attempted to read Testcontainers configuration file at file:/Users/dario/.testcontainers.properties but the file was not found. Exception message: FileNotFoundException: /Users/dario/.testcontainers.properties (No such file or directory)
2022-10-27 18:07:29,653 INFO  [org.tes.doc.DockerMachineClientProviderStrategy] (build-25) docker-machine executable was not found on PATH ([/Users/dario/projects/sdkman/candidates/springboot/current/bin, /Users/dario/projects/sdkman/candidates/quarkus/current/bin, /Users/dario/projects/sdkman/candidates/java/current/bin, /Users/dario/Library/Android/sdk/platform-tools, /Users/dario/Library/Android/sdk/tools/bin, /Users/dario/Library/Android/sdk/tools, /Users/dario/bin, /usr/local/bin, /System/Cryptexes/App/usr/bin, /usr/bin, /bin, /usr/sbin, /sbin, /usr/local/go/bin, /Library/Apple/usr/bin])

2022-10-27 18:07:29,655 ERROR [org.tes.doc.DockerClientProviderStrategy] (build-25) Could not find a valid Docker environment. Please check configuration. Attempted configurations were:
2022-10-27 18:07:29,657 ERROR [org.tes.doc.DockerClientProviderStrategy] (build-25)     UnixSocketClientProviderStrategy: failed with exception InvalidConfigurationException (Could not find unix domain socket). Root cause NoSuchFileException (/var/run/docker.sock)
2022-10-27 18:07:29,658 ERROR [org.tes.doc.DockerClientProviderStrategy] (build-25) As no valid configuration was found, execution cannot continue
2022-10-27 18:07:30,026 INFO  [org.tes.uti.ImageNameSubstitutor] (build-25) Image name substitution will be performed by: DefaultImageNameSubstitutor (composite of 'ConfigurationFileImageNameSubstitutor' and 'PrefixingImageNameSubstitutor')
2022-10-27 18:07:30,038 INFO  [io.qua.dep.dev.IsolatedDevModeMain] (main) Attempting to start live reload endpoint to recover from previous Quarkus startup failure
2022-10-27 18:07:30,279 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.RuntimeException: java.lang.IllegalStateException: Previous attempts to find a Docker environment failed. Will not retry. Please see logs and check configuration
	at io.quarkus.oidc.deployment.devservices.keycloak.KeycloakDevServicesProcessor.startKeycloakContainer(KeycloakDevServicesProcessor.java:244)
...

So then I have stopped Docker and quarkus dev doesn't tell me nothing about Docker, Keycloak, and so on.

[InfoSec812]

Ahhh... Yes, I have seen similar issues on MacOS... Try setting the variable export DOCKER_HOST=unix://$HOME/.docker/run/docker.sock

[dscoppelletti]

Yes, I work on MacOS.
I have set the DOCKER_HOST environment variable.
Now quarkus dev emits:

...
Checking Docker Environment 2022-10-27 18:53:36,382 INFO  [🐳 .3.3]] (build-32) Container testcontainers/ryuk:0.3.3 is starting: f939907455ea77bf4f44bd287ed626828734efac9dd564ffa5bdecfe327f7eed
Keycloak Dev Services Starting: 2022-10-27 18:53:36,382 INFO  [🐳 .3.3]] (build-32) Container testcontainers/ryuk:0.3.3 is starting: f939907455ea77bf4f44bd287ed626828734efac9dd564ffa5bdecfe327f7eed
...
--
--
Checking Docker Environment 2022-10-27 18:53:36,382 INFO  [🐳 .3.3]] (build-32) Container testcontainers/ryuk:0.3.3 is starting: f939907455ea77bf4f44bd287ed626828734efac9dd564ffa5bdecfe327f7eed
Keycloak Dev Services Starting: 2022-10-27 18:53:36,819 ERROR [🐳 .3.3]] (build-32) Could not start container: com.github.dockerjava.api.exception.NotFoundException: Status 404: {"message":"No such container: f939907455ea77bf4f44bd287ed626828734efac9dd564ffa5bdecfe327f7eed"}	at org.testcontainers.shaded.com.github.dockerjava.core.DefaultInvocationBuilder.execute(DefaultInvocationBuilder.java:241)
...

However, thanks for the step forward.

[InfoSec812]

OK, the next step for me was creating the file ~/.testcontainers.properties with the content ryuk.container.privileged=true

[dscoppelletti]

Now quarkus emits:

Checking Docker Environment 2022-11-02 17:35:48,691 INFO  [🐳 .3.3]] (build-44) Container testcontainers/ryuk:0.3.3 is starting: a45a701cded20c5d50f0f31078185828adbcec1d08042f68d9ad9f00c055c90c
Keycloak Dev Services Starting: 2022-11-02 17:35:48,691 INFO  [🐳 .3.3]] (build-44) Container testcontainers/ryuk:0.3.3 is starting: a45a701cded20c5d50f0f31078185828adbcec1d08042f68d9ad9f00c055c90c

But when I try to access `http://localhost:8080/q/dev", it fails:

Checking Docker Environment 2022-11-02 17:36:49,043 ERROR [🐳 .3.3]] (build-44) Could not start container: java.lang.IllegalStateException: Container is removeat org.testcontainers.containers.GenericContainer.tryStart(GenericContainer.java:496)	at org.testcontainers.containers.GenericContainer.lambda$doStart$0(GenericContainer.java:344)
[...]
2022-11-02 17:35:48,560 INFO  [org.tes.uti.RegistryAuthLocator] (build-44) Crede2022-11-02 17:35:48,691 INFO  [🐳 .3.3]] (build-44) Container testcontainers/ryuk:0.3.3 is starting: a45a701cded20c5d50f0f31078185828adbcec1d08042f68d9ad9f00c055c90ctcontainers/ryuk:0.3.3DockerStatusBuildItem.isDockerAvailable(DockerStatusB2022-11-02 17:36:49,043 ERROR [🐳 .3.3]] (build-44) Could not start container: java.lang.IllegalStateException: Container is removedSubstitutor] (build-44) Image name sat org.testcontainers.containers.GenericContainer.tryStart(GenericContainer.java:496)
[...]
2022-11-02 17:36:49,052 ERROR [🐳 .3.3]] (build-44) There are no stdout/stderr logs available for the failed container
2022-11-02 17:36:49,461 INFO  [io.qua.dep.dev.IsolatedDevModeMain] (main) Attempting to start live reload endpoint to recover from previous Quarkus startup failure
2022-11-02 17:36:49,743 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.RuntimeException: org.testcontainers.containers.ContainerLaunchException: Container startup failed
	at io.quarkus.oidc.deployment.devservices.keycloak.KeycloakDevServicesProcessor.startKeycloakContainer(KeycloakDevServicesProcessor.java:244)
[...]
Caused by: java.lang.RuntimeException: org.testcontainers.containers.ContainerLaunchException: Container startup failed
	at io.quarkus.oidc.deployment.devservices.keycloak.KeycloakDevServicesProcessor.startKeycloakContainer(KeycloakDevServicesProcessor.java:244)
[...]
Caused by: org.testcontainers.containers.ContainerLaunchException: Could not create/start container
	at org.testcontainers.containers.GenericContainer.tryStart(GenericContainer.java:542)

I think to give a try to podman, but now I can't because I must use Docker for another project.