Replies: 4 comments 2 replies
-
|
Seems like ryuk (test containers container for cleanup) fails to start in your environment. Sometimes it needs to start as a privileged container maybe that's what's failing. Can you retry by disabling it with export TESTCONTAINERS_RYUK_DISABLED=true? |
Beta Was this translation helpful? Give feedback.
-
|
It seems that disabling it helps 2021-12-26 18:05:35,479 INFO [org.tes.DockerClientFactory] (docker-java-stream--1128992070) Starting to pull image
2021-12-26 18:05:35,493 INFO [org.tes.DockerClientFactory] (docker-java-stream--1128992070) Pulling image layers: 0 pending, 0 downloaded, 0 extracted, (0 bytes/0 bytes)
2021-12-26 18:05:36,746 INFO [org.tes.DockerClientFactory] (docker-java-stream--1128992070) Pulling image layers: 0 pending, 1 downloaded, 0 extracted, (943 KB/2 MB)
2021-12-26 18:05:36,830 INFO [org.tes.DockerClientFactory] (docker-java-stream--1128992070) Pulling image layers: 0 pending, 1 downloaded, 1 extracted, (2 MB/2 MB)
2021-12-26 18:05:36,842 INFO [org.tes.DockerClientFactory] (docker-java-stream--1128992070) Pull complete. 1 layers, pulled in 1s (downloaded 2 MB at 2 MB/s)
2021-12-26 18:05:39,372 INFO [🐳 .io/.5.5]] (docker-java-stream--2132549693) Starting to pull image
2021-12-26 18:05:39,373 INFO [🐳 .io/.5.5]] (docker-java-stream--2132549693) Pulling image layers: 0 pending, 0 downloaded, 0 extracted, (0 bytes/0 bytes)
2021-12-26 18:05:39,950 INFO [🐳 .io/.5.5]] (docker-java-stream--2132549693) Pulling image layers: 6 pending, 1 downloaded, 0 extracted, (335 bytes/? MB)
2021-12-26 18:05:40,545 INFO [🐳 .io/.5.5]] (docker-java-stream--2132549693) Pulling image layers: 5 pending, 2 downloaded, 0 extracted, (39 MB/? MB)
2021-12-26 18:05:40,669 INFO [🐳 .io/.5.5]] (docker-java-stream--2132549693) Pulling image layers: 4 pending, 3 downloaded, 0 extracted, (50 MB/? MB)
2021-12-26 18:05:41,102 INFO [🐳 .io/.5.5]] (docker-java-stream--2132549693) Pulling image layers: 4 pending, 3 downloaded, 1 extracted, (55 MB/? MB)
2021-12-26 18:05:41,213 INFO [🐳 .io/.5.5]] (docker-java-stream--2132549693) Pulling image layers: 3 pending, 4 downloaded, 1 extracted, (55 MB/? MB)
2021-12-26 18:05:41,247 INFO [🐳 .io/.5.5]] (docker-java-stream--2132549693) Pulling image layers: 2 pending, 5 downloaded, 1 extracted, (55 MB/? MB)
2021-12-26 18:05:41,294 INFO [🐳 .io/.5.5]] (docker-java-stream--2132549693) Pulling image layers: 2 pending, 5 downloaded, 2 extracted, (58 MB/? MB)
2021-12-26 18:05:41,337 INFO [🐳 .io/.5.5]] (docker-java-stream--2132549693) Pulling image layers: 2 pending, 5 downloaded, 3 extracted, (58 MB/? MB)
2021-12-26 18:05:41,379 INFO [🐳 .io/.5.5]] (docker-java-stream--2132549693) Pulling image layers: 2 pending, 5 downloaded, 4 extracted, (58 MB/? MB)
2021-12-26 18:05:41,423 INFO [🐳 .io/.5.5]] (docker-java-stream--2132549693) Pulling image layers: 2 pending, 5 downloaded, 5 extracted, (58 MB/? MB)
2021-12-26 18:05:41,464 INFO [🐳 .io/.5.5]] (docker-java-stream--2132549693) Pulling image layers: 2 pending, 5 downloaded, 6 extracted, (58 MB/? MB)
2021-12-26 18:05:44,385 INFO [🐳 .io/.5.5]] (docker-java-stream--2132549693) Pulling image layers: 1 pending, 6 downloaded, 6 extracted, (259 MB/? MB)
2021-12-26 18:05:47,186 INFO [🐳 .io/.5.5]] (docker-java-stream--2132549693) Pulling image layers: 1 pending, 6 downloaded, 7 extracted, (260 MB/? MB)
2021-12-26 18:05:47,197 INFO [🐳 .io/.5.5]] (docker-java-stream--2132549693) Pull complete. 7 layers, pulled in 7s (downloaded 260 MB at 37 MB/s)
2021-12-26 18:05:49,473 INFO [io.qua.kaf.cli.dep.DevServicesKafkaProcessor] (build-15) Dev Services for Kafka started. Other Quarkus applications in dev mode will find the broker automatically. For Quarkus applications in production mode, you can connect to this by starting your application with -Dkafka.bootstrap.servers=OUTSIDE://localhost:49161
One or more configuration errors have prevented the application from starting. The errors are:
- SRCFG00014: The config property quarkus.kafka-streams.topics is required but it could not be found in any config source
2021-12-26 18:05:49,928 INFO [io.qua.dep.dev.IsolatedDevModeMain] (main) Attempting to start live reload endpoint to recover from previous Quarkus startup failure
2021-12-26 18:05:49,928 INFO [io.qua.dep.dev.IsolatedDevModeMain] (main) Attempting to start live reload endpoint to recover from previous Quarkus startup failure
2021-12-26 18:05:49,960 DEBUG [org.jbo.threads] (main) JBoss Threads version 3.4.2.Final
2021-12-26 18:05:50,026 ERROR [io.qua.dep.dev.IsolatedDevModeMain] (main) Failed to start quarkus: java.lang.RuntimeException: java.lang.RuntimeException: Failed to start quarkus
at io.quarkus.dev.appstate.ApplicationStateNotification.waitForApplicationStart(ApplicationStateNotification.java:51)
at io.quarkus.runner.bootstrap.StartupActionImpl.runMainClass(StartupActionImpl.java:122)
at io.quarkus.deployment.dev.IsolatedDevModeMain.firstStart(IsolatedDevModeMain.java:145)
at io.quarkus.deployment.dev.IsolatedDevModeMain.accept(IsolatedDevModeMain.java:456)
at io.quarkus.deployment.dev.IsolatedDevModeMain.accept(IsolatedDevModeMain.java:67)
at io.quarkus.bootstrap.app.CuratedApplication.runInCl(CuratedApplication.java:149)
at io.quarkus.bootstrap.app.CuratedApplication.runInAugmentClassLoader(CuratedApplication.java:105)
at io.quarkus.deployment.dev.DevModeMain.start(DevModeMain.java:145)
at io.quarkus.deployment.dev.DevModeMain.main(DevModeMain.java:63)
Caused by: java.lang.RuntimeException: Failed to start quarkus
at io.quarkus.runner.ApplicationImpl.doStart(Unknown Source)
at io.quarkus.runtime.Application.start(Application.java:101)
at io.quarkus.runtime.ApplicationLifecycleManager.run(ApplicationLifecycleManager.java:104)
at io.quarkus.runtime.Quarkus.run(Quarkus.java:67)
at io.quarkus.runtime.Quarkus.run(Quarkus.java:41)
at io.quarkus.runtime.Quarkus.run(Quarkus.java:120)
at io.quarkus.runner.GeneratedMain.main(Unknown Source)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at io.quarkus.runner.bootstrap.StartupActionImpl$1.run(StartupActionImpl.java:103)
at java.base/java.lang.Thread.run(Thread.java:829)
Caused by: io.quarkus.runtime.configuration.ConfigurationException: One or more configuration errors have prevented the application from starting. The errors are:
- SRCFG00014: The config property quarkus.kafka-streams.topics is required but it could not be found in any config sourceThe error is now related to missing topics configuration parameter that anyway doesn't sound so great to me because anyone should be able just to start the app even without any usage of topics even if I referenced the Kafka Streams dependency there. But it could be a Quarkus developer choice to enforce the parameter to be set because you are working with Kafka. |
Beta Was this translation helpful? Give feedback.
-
|
I was reading about this ryuk ... and I have never used test containers as well. Reading about it, isn't it pretty bad having on you own env a container running as a privileged container so "have root privilege to the host machine"??? |
Beta Was this translation helpful? Give feedback.
-
|
It comes from Test Containers. To be honest, nobody complains before, and there is a way to disable Riuk if you don't want it. Note that Ryuk is kind of a watchdog, it can be really useful to make sure your containers got stopped (and not kept running for days without noticing anything). Also, if you do not want to use Dev Services, just start your own kafka cluster and configure the bootstrap.servers. |
Beta Was this translation helpful? Give feedback.
-
|
From my perspective, just creating an empty project and adding a Kafka dependency and then running having this issue is not a great experience from a user point of view. If test containers is about testing and I am running the application why it comes into the picture. After disabling it, the run also complains about not setting a topics config parameter; I didn't enter into the rabbit hole yet but still even this doesn't sound a good experience. But I will come later on this with more thoughts. For now I would just expect that an empty project just runs fine. |
Beta Was this translation helpful? Give feedback.
-
As far as I understood from the Quarkus doc, if I add any Kafka related extension to a Quarkus application it should start a container with a Redpanda based Kafka broker.
I created an empty project using the extension in VSCode adding the Kafka Streams extension but not adding any code (so just leaving the
GreetingResource.javafile only) and just runmvn quarkus:devbut got the following error:Beta Was this translation helpful? Give feedback.
All reactions