Fix docker compose up in sirix-rest-api
JohannesLichtenberger opened this issue · comments
Fix docker compose up regarding the Github Action (currently the tests fail)...
hi, can you give same info for the problem?
The Github Action currently fails, because something apparently fails during the Docker container start, but I'm not sure how to log the error and locally it starts fine: https://github.com/sirixdb/sirix/actions/runs/8305202119
johannes@luna:~/IdeaProjects/sirix/bundles/sirix-rest-api/src/test/resources$ sudo docker compose -f docker-compose.yml --ansi never -p sirix-test up -d
Container sirix-test-keycloak-1 Starting
Container sirix-test-keycloak-1 Started
2024-03-17T04:09:05.0425707Z 2024-03-17T04:09:04.433+0000 [INFO] [org.gradle.process.internal.DefaultExecHandle] Starting process 'command 'docker''. Working directory: /home/runner/work/sirix/sirix/bundles/sirix-rest-api Command: docker compose -f /home/runner/work/sirix/sirix/bundles/sirix-rest-api/src/test/resources/docker-compose.yml --ansi never -p sirix-test up -d
2024-03-17T04:09:05.0429169Z 2024-03-17T04:09:04.433+0000 [DEBUG] [org.gradle.process.internal.DefaultExecHandle] Changing state to: STARTING
2024-03-17T04:09:05.0497857Z 2024-03-17T04:09:04.435+0000 [DEBUG] [org.gradle.process.internal.DefaultExecHandle] Waiting until process started: command 'docker'.
2024-03-17T04:09:05.0499946Z 2024-03-17T04:09:04.449+0000 [DEBUG] [org.gradle.process.internal.DefaultExecHandle] Changing state to: STARTED
2024-03-17T04:09:05.0501876Z 2024-03-17T04:09:04.449+0000 [DEBUG] [org.gradle.process.internal.ExecHandleRunner] waiting until streams are handled...
2024-03-17T04:09:05.0504160Z 2024-03-17T04:09:04.449+0000 [INFO] [org.gradle.process.internal.DefaultExecHandle] Successfully started process 'command 'docker''
2024-03-17T04:09:05.0506126Z 2024-03-17T04:09:04.862+0000 [DEBUG] [org.gradle.process.internal.DefaultExecHandle] Changing state to: FAILED
2024-03-17T04:09:05.0508332Z 2024-03-17T04:09:04.863+0000 [DEBUG] [org.gradle.process.internal.DefaultExecHandle] Process 'command 'docker'' finished with exit value 18 (state: FAILED)
2024-03-17T04:09:05.0510482Z 2024-03-17T04:09:04.865+0000 [DEBUG] [org.gradle.api.Task] Failed to start-up Docker containers
2024-03-17T04:09:05.0512484Z java.lang.RuntimeException: Exit-code 18 when calling docker-compose, stdout: java.io.FileOutputStream@5c88feed
2024-03-17T04:09:05.0514380Z at java.base/jdk.internal.reflect.DirectConstructorHandleAccessor.newInstance(DirectConstructorHandleAccessor.java:62)
2024-03-17T04:09:05.0516228Z at java.base/java.lang.reflect.Constructor.newInstanceWithCaller(Constructor.java:502)
2024-03-17T04:09:05.0517543Z at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:486)
2024-03-17T04:09:05.0518855Z at org.codehaus.groovy.reflection.CachedConstructor.invoke(CachedConstructor.java:72)
2024-03-17T04:09:05.0520426Z at org.codehaus.groovy.reflection.CachedConstructor.doConstructorInvoke(CachedConstructor.java:59)
...
can I look into this?
@Stredsto any progress already?
Hey @JohannesLichtenberger,
I was having some setup issues, also got a little busy at work, will continue again on this today.
Finish any setup issues and then this
Hello @JohannesLichtenberger .
I continued with the setup again, I am able to start the docker for keycloak, but docker image for sirixdb just wont get up,
I believe this is what I have to start to run the main application because if I directly run Main.java from intellij, that's just keep running for hours.
That's the main issue I guess, that the container for some reason doesn't start. Can you check the docker log for the container?
yeah looking through it
yeah looking through it
[vert.x-eventloop-thread-0] ERROR i.v.c.i.l.c.VertxIsolatedDeployer - Failed in deploying verticle
io.vertx.core.impl.NoStackTraceThrowable: Not Found: {"error":"Unable to find matching target resource method","error_description":"For more on this error consult the server log at the debug level."}
any idea, what does this error exactly means?
hey @JohannesLichtenberger, is this fixed by someone ?
I've fixed the docker image specification, as it didn't exist anymore (quay.io/keycloak/keycloak:7.0.1 instead of jboss/keycloak:7.0.1).
That said we have to update to the newest keycloak version and check why it doesn't start anymore.
@JohannesLichtenberger keycloak starts well in my local docker setup
keycloak: image: quay.io/keycloak/keycloak ports: - 8080:8080 - 8433:8433 environment: - KEYCLOAK_USER=admin - KEYCLOAK_ADMIN=admin - KEYCLOAK_PASSWORD=admin - KEYCLOAK_ADMIN_PASSWORD=admin - KEYCLOAK_LOGLEVEL=DEBUG - KEYCLOAK_IMPORT=/opt/keycloak/realm-export.json restart: always
tho I had to add these :
KEYCLOAK_ADMIN=admin
KEYCLOAK_ADMIN_PASSWORD=admin
@Stredsto you like to make a PR? There's a docker compose file in the parent directory (project root), one in sirix-rest-api/src/test/resources and one in the sirix-python-client :-)
@JohannesLichtenberger Sure, I'll do the PR