orpiske commented on issue #25: Integrations tests fails if 
confluentinc/cp-kafka:5.2.1 has not been pulled
URL: 
https://github.com/apache/camel-kafka-connector/issues/25#issuecomment-564888054
 
 
   > It seems that the problem was somehow related to my docker environment 
being tainted somehow.
   > 
   > Starting from a fresh docker environment (i.e. by stopping docker deamon, 
forcefully removing `/var/lib/docker` directory and starting the docker deamon 
again) the error disappeared.
   
   Hey, this is great. I couldn't find much by looking at the logs, but I found 
some occurrences about this issue on the internet and on a few of them people 
were claiming that the issue would go away with a ```docker system prune```. I 
was a bit skeptical as you did not seem to have problems outside the test 
suite, but apparently it may have some effect after all. 
   
   > 
   > Here are the images pulled as a result of a fresh `mvn clean install`:
   > 
   > ```
   > REPOSITORY                                          TAG                 
IMAGE ID            CREATED             SIZE
   > centos                                              8                   
0f3e07c0138f        2 months ago        220MB
   > docker.elastic.co/elasticsearch/elasticsearch-oss   7.3.2               
876f2f753cc8        3 months ago        612MB
   > localstack/localstack                               0.9.4               
5c6c5a293024        6 months ago        1.29GB
   > confluentinc/cp-kafka                               5.2.1               
af7cf4356c58        8 months ago        569MB
   > quay.io/testcontainers/ryuk                         0.2.3               
64849fd2d464        10 months ago       10.7MB
   > alpine                                              3.5                 
f80194ae2e0c        10 months ago       4MB
   > ```
   > 
   That looks good! That's what I have here :) 
   
   > @orpiske I don't remember if you were working on removing the need for 
`confluentinc/cp-kafka` replacing it with some upstream alternative?
   
   Yes I am. I needed to get some patches out of the way first (like #29 and 
#42) - and then focus on this issue - and now I am going to work on this. 
   
   
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

Reply via email to