testcontainers / testcontainers/testcontainers-python

Bug: trying to run localstack test container under bitbucket

Abierto
#564 3 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Lenguaje dominante
Python
Estrellas
2.3k
Forks
386
Merge medio
4 h 40 min
PR fusionados (30 d)
1

Descripción

Describe the bug

Not sure if this is testcontainers or localstack, I have a testcontainers localstack image running on bitbucket the only different is the pro version. Anyone else had this or do I need to get localstack support?

integration_tests/test_stitched_consumptions_glue.py::test_stitched_consumptions_perfect_consumptions 

-------------------------------- live log setup --------------------------------

2024-05-07 13:24:27 [    INFO] using host 10.38.132.27:2375 (docker_client.py:52)

2024-05-07 13:24:27 [   DEBUG] Trying paths: ['/nonexistent/.docker/config.json', '/nonexistent/.dockercfg'] ([config.py:21](http://config.py:21/))

2024-05-07 13:24:27 [   DEBUG] No config file found ([config.py:28](http://config.py:28/))

2024-05-07 13:24:27 [   DEBUG] Trying paths: ['/nonexistent/.docker/config.json', '/nonexistent/.dockercfg'] ([config.py:21](http://config.py:21/))

2024-05-07 13:24:27 [   DEBUG] No config file found ([config.py:28](http://config.py:28/))

2024-05-07 13:24:27 [   DEBUG] Starting new HTTP connection (1): 10.38.132.27:2375 ([connectionpool.py:246](http://connectionpool.py:246/))

2024-05-07 13:24:27 [   DEBUG] http://10.38.132.27:2375/ "GET /version HTTP/1.1" 200 821 ([connectionpool.py:474](http://connectionpool.py:474/))

2024-05-07 13:24:27 [    INFO] using host 10.38.132.27:2375 (docker_client.py:52)

2024-05-07 13:24:27 [   DEBUG] Trying paths: ['/nonexistent/.docker/config.json', '/nonexistent/.dockercfg'] ([config.py:21](http://config.py:21/))

2024-05-07 13:24:27 [   DEBUG] No config file found ([config.py:28](http://config.py:28/))

2024-05-07 13:24:27 [   DEBUG] Trying paths: ['/nonexistent/.docker/config.json', '/nonexistent/.dockercfg'] ([config.py:21](http://config.py:21/))

2024-05-07 13:24:27 [   DEBUG] No config file found ([config.py:28](http://config.py:28/))

2024-05-07 13:24:27 [   DEBUG] Starting new HTTP connection (1): 10.38.132.27:2375 ([connectionpool.py:246](http://connectionpool.py:246/))

2024-05-07 13:24:27 [   DEBUG] http://10.38.132.27:2375/ "GET /version HTTP/1.1" 200 821 ([connectionpool.py:474](http://connectionpool.py:474/))

2024-05-07 13:24:27 [    INFO] Pulling image testcontainers/ryuk:0.7.0 ([container.py:88](http://container.py:88/))

2024-05-07 13:24:27 [   DEBUG] http://10.38.132.27:2375/ "POST /v1.44/containers/create?name=testcontainers-ryuk-88fe3177-a1c8-43b0-9b4b-e5e298b46f84 HTTP/1.1" 404 55 ([connectionpool.py:474](http://connectionpool.py:474/))

2024-05-07 13:24:27 [   DEBUG] Looking for auth config ([auth.py:39](http://auth.py:39/))

2024-05-07 13:24:27 [   DEBUG] No auth config in memory - loading from filesystem ([auth.py:41](http://auth.py:41/))

2024-05-07 13:24:27 [   DEBUG] Trying paths: ['/nonexistent/.docker/config.json', '/nonexistent/.dockercfg'] ([config.py:21](http://config.py:21/))

2024-05-07 13:24:27 [   DEBUG] No config file found ([config.py:28](http://config.py:28/))

2024-05-07 13:24:27 [   DEBUG] Looking for auth entry for '[docker.io](http://docker.io/)' ([auth.py:231](http://auth.py:231/))

2024-05-07 13:24:27 [   DEBUG] No entry found ([auth.py:242](http://auth.py:242/))

2024-05-07 13:24:27 [   DEBUG] No auth config found ([auth.py:56](http://auth.py:56/))

2024-05-07 13:24:27 [   DEBUG] http://10.38.132.27:2375/ "POST /v1.44/images/create?tag=0.7.0&fromImage=testcontainers%2Fryuk HTTP/1.1" 200 None ([connectionpool.py:474](http://connectionpool.py:474/))

2024-05-07 13:24:30 [   DEBUG] http://10.38.132.27:2375/ "GET /v1.44/images/testcontainers/ryuk:0.7.0/json HTTP/1.1" 200 2048 ([connectionpool.py:474](http://connectionpool.py:474/))

Guía de contribución

Abrir la guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Línea de trabajo

Comienza con integration_tests/test_stitched_consumptions_glue.py::test_stitched_consumptions_perfect_consumptions y reproduce la ejecución de Bitbucket usando el endpoint de Docker mostrado en los logs. Inspecciona las solicitudes de pull y creación de contenedores de testcontainers/ryuk:0.7.0 y, después, documenta o prueba el comportamiento que distingue este entorno de la configuración localstack indicada.

Escrito por el modelo de indexación a partir del texto del issue.

Evaluación

Stack tecnológico
docker, python
Área
ci-cd, testing-qa
Tipo de issue
Error
Dificultad
4/5
Tiempo estimado
3-5 días
Estado de actividad
Estancado
Claridad
Necesita aclaración
Aptitud para principiantes
20/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.