testcontainers / testcontainers/testcontainers-java
DockerClientConfigUtils#getDefaultGateway() is failing with syslog driver
Nadie ha tomado este issue todavía.
- Lenguaje dominante
- Java
- Estrellas
- 8.7k
- Forks
- 1.9k
- Merge medio
- 2 d 17 h
- PR fusionados (30 d)
- 9
Descripción
Hello guys,
I'm trying to use testcontainers-java (which I like a lot) and I can't make it work in my CI infrastructure.
The reason of the failure is because I'm running my tests inside docker and the docker logging driver is configured to syslog.
For what I understood, this code is trying to read the log to get the output of a command to get the gateway ip and it's failing because getting the log is not supported by syslog.
Therefore the gateway ip address can not be determined and the library can not properly manage containers.
I'm getting the following error in the logs of my build:
10:11:34.252 [tc-okhttp-stream-247575268] ERROR com.github.dockerjava.core.async.ResultCallbackTemplate - Error during callback
com.github.dockerjava.api.exception.InternalServerErrorException: {"message":"configured logging reader does not support reading"}
It looks like an issue to me as the library can not be used with such configuration. I'd like to have your thoughts on that and eventually know if there could be any workaround I could use.
Thank in advance !
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Línea de trabajo
Comienza en core/src/main/java/org/testcontainers/dockerclient/DockerClientConfigUtils.java, en getDefaultGateway(), y luego reproduce el fallo con el syslog logging driver de Docker. Sigue cómo se obtienen la salida del comando y la gateway IP, y verifica que Testcontainers pueda determinar la gateway sin el error de logging-reader no compatible.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- docker, java
- Área
- devops, testing
- Tipo de issue
- Error
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Estado de actividad
- Estancado
- Claridad
- Bastante claro
- Aptitud para principiantes
- 35/100