testcontainers / testcontainers/testcontainers-python
Bug: trying to run localstack test container under bitbucket
Dieses Issue hat noch niemand übernommen.
- Vorherrschende Sprache
- Python
- Sterne
- 2.3k
- Forks
- 386
- Ø Merge
- 4 Std. 40 Min.
- Gemergte PRs (30 T.)
- 1
Beschreibung
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/))
Beitragsleitfaden
Erste Schritte
- Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
- Forke das Repository und arbeite in einem Branch.
- Öffne einen Pull Request, der die Issue-Nummer nennt.
Rechercherichtung
Beginne mit integration_tests/test_stitched_consumptions_glue.py::test_stitched_consumptions_perfect_consumptions und reproduziere den Bitbucket-Lauf mithilfe des in den Logs gezeigten Docker-Endpunkts. Untersuche die Pull- und Container-Erstellungsanfragen für testcontainers/ryuk:0.7.0 und dokumentiere oder teste anschließend das Verhalten, das diese Umgebung vom gemeldeten localstack-Setup unterscheidet.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- docker, python
- Bereich
- ci-cd, testing-qa
- Issue-Typ
- Bug
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Aktivitätsstatus
- Veraltet
- Klarheit
- Muss geklärt werden
- Anfängerfreundlichkeit
- 20/100