Sababta Testcontainers withEnv uusan u marin jiidista sawirka proxy
Habee daemon-ka Docker jiidid fashilantay; doorsoomayaasha proxy ee container-ka waxay gaaraan barnaamijyada kaliya ka dib marka container-ka la abuuro.
Haddii Testcontainers ku fashilmo inta sawir la jiidanayo, dejinta withEnv ee container-ka soo socda ma caawin karto. Daemon-ka Docker ayaa sameeya jiididdaas diiwaanka ka hor inta uusan container-ku jirin.
| Hawl fashilantay | Dejinta proxy ee la baarayo |
|---|---|
| Jiidista sawirka | Daemon-ka Docker ee imtixaanku isticmaalo iyo wadadiisa diiwaanka |
| Soo dejinta gudaha container-ka socda | Gelinta ay barnaamijku taageerto container-kaas |
| Imtixaanka Java wuxuu ku xirmo Docker ama barnaamijka | Macaamilka Java ee sameeya xiriirkaas |
Kiiska labaad, ku dar doorsoomayaal deegaan qeexitaanka GenericContainer ee jira:
container
.withEnv("http_proxy", "http://proxy.example:8080")
.withEnv("https_proxy", "http://proxy.example:8080");Haddii soo dejinta gudaha container-ka loo ogolaado inuu isticmaalo barta HTTP ee dadweynaha, buuxi qiyamkaas laga bilaabo liiska proxy HTTP. Barnaamijka ku jira sawirka waa inuu akhriyaa doorsoomayaashaas. Kama beddelaan socket-ka xogta macquulka ah taraafikada proxy HTTP. Barta sidoo kale waa in laga gaari karaa container-ka: 127.0.0.1 waxay tilmaamaysaa isaga laftiisa.
Kiiska koowaad, raadi deegaanka Docker ee Testcontainers dhab ahaan isticmaalo. Daemon fog ama Docker Desktop ayaa laga yaabaa inay dejinta ka qaataan ilo ka duwan dockerd maxalli ah. Ku hay adeegyada imtixaanka maxalliga ah iyo Docker API waddooyinkooda loogu talagalay markaad ku darayso proxy caadi ah oo ballaaran.