Closed antz-H closed 7 months ago
The second test case problem
15:47:16.351 [docker-java-stream--333906299] ERROR com.github.dockerjava.api.async.ResultCallbackTemplate - Error during callback
com.github.dockerjava.api.exception.InternalServerErrorException: Status 500: {"message":"Head \"https://registry-1.docker.io/v2/testcontainers/ryuk/manifests/0.3.1\": unauthorized: incorrect username or password"}
at org.testcontainers.shaded.com.github.dockerjava.core.DefaultInvocationBuilder.execute(DefaultInvocationBuilder.java:247) ~[testcontainers-1.15.3.jar:?]
at org.testcontainers.shaded.com.github.dockerjava.core.DefaultInvocationBuilder.lambda$executeAndStream$1(DefaultInvocationBuilder.java:269) ~[testcontainers-1.15.3.jar:?]
at java.lang.Thread.run(Thread.java:840) [?:?]
Status 500: {"message":"Head \"https://registry-1.docker.io/v2/testcontainers/ryuk/manifests/0.3.1\": unauthorized: incorrect username or password"}
com.github.dockerjava.api.exception.InternalServerErrorException: Status 500: {"message":"Head \"https://registry-1.docker.io/v2/testcontainers/ryuk/manifests/0.3.1\": unauthorized: incorrect username or password"}
at app//org.testcontainers.shaded.com.github.dockerjava.core.DefaultInvocationBuilder.execute(DefaultInvocationBuilder.java:247)
at app//org.testcontainers.shaded.com.github.dockerjava.core.DefaultInvocationBuilder.lambda$executeAndStream$1(DefaultInvocationBuilder.java:269)
at java.base@17.0.10/java.lang.Thread.run(Thread.java:840)
I review the source code(3.16.0) of condutor for some time. And this for beginner' guide.
The first mistake above is because of the Flyway's version issue. The second mistake above is beacause of the docker-hub environment issue when you want to run test .
Others.
The conductor support different deployment architecture.
If you want to change (such as use the es), you should build from source code .
So review the source code is more important , because the official docs are too few.
First shoud to review the code , i think is the module-- docker, there you can find many what you want, such as how to build , how to start(run) .
Second if you want to change the deployment architecture , you should build your own image.
Welcome to correct my mistakes.
If you want to use the conductoross/conductor:3.15.0 in prod , you can run with below command line like this
docker run -v C://home//tmp//conductor//config-redis_postgres.properties:/app/config/config.properties --init -p 8080:8080 -p 1234:5000 conductoross/conductor:3.15.0
congfig.properties
# Database persistence type.
# Below are the properties for redis
conductor.db.type=redis_standalone
conductor.queue.type=redis_standalone
conductor.redis.hosts=127.0.0.1:6379:us-east-1c
conductor.redis-lock.serverAddress=redis://127.0.0.1:6379
conductor.redis.taskDefCacheRefreshInterval=1
conductor.redis.workflowNamespacePrefix=conductor
conductor.redis.queueNamespacePrefix=conductor_queues
spring.datasource.url=jdbc:postgresql://127.0.0.1:5432/conductor
spring.datasource.username=postgres
spring.datasource.password=root
# Additional modules for metrics collection exposed to Prometheus (optional)
conductor.metrics-prometheus.enabled=true
management.endpoints.web.exposure.include=prometheus
# Load sample kitchen sink workflow
loadSample=true
I just wanted to document the Unit-Test problems I encountered through this, so that other people might also encounter them.
I run the source code on my window-system , the execute the test case , it reported errors.
source code version : v3.16.0
this is full of error message