Podman pasta: isa ga proxy loopback na host daga container mara root

Yi amfani da jigilar TCP na pasta daga namespace zuwa host don proxy loopback da ke akwai, kuma ka raba shi da buga tashar container.

127.0.0.1:8118 na host da 127.0.0.1:8118 na container yawanci mabanbantan wuraren ƙarshen loopback ne. Shigar da masaukin proxy a cikin container mara root ba ya haɗa waɗannan mu'amalolin loopback.

A cikin tura Podman da ke amfani da pasta, jigilar TCP daga namespace zuwa host na iya fallasa tashar host da ake so a cikin namespace:

podman run --network=pasta:-T,8118 \
  --env http_proxy=http://127.0.0.1:8118 \
  --env https_proxy=http://127.0.0.1:8118 \
  existing-image application-command

Yi amfani da hoton da umarnin aikace-aikacen da ke akwai. Misalin yana ɗauka cewa akwai HTTP proxy mai aiki a gefen host a tashar 8118 da sigar Podman/pasta da ke goyan bayan zaɓin jigila da aka nuna.

Babban -T na pasta yana jigila daga namespace na manufa zuwa namespace na host. Ƙaramin -t da --publish na Podman suna fuskantar akasin alkibla. Don haka buga tashar container 8118 ba ya sa proxy na host ya zama samuwa ga container da kansa.

Podman yana kashe jigilar tashoshi ta atomatik daga namespace zuwa host bisa tsoho; bayyanannen tasha yana zaɓar sabis ɗin da ake buƙata a nan. Zaɓin pasta:--map-gw daban yana magana ne kan isa host ta adireshin ƙofar, wanda wani tsari ne.

Tare da Compose, duba ainihin mai bayarwa da tsarin cibiyar sadarwar da aka ƙirƙira. Cibiyar sadarwar gada mai suna ba ta zama namespace na pasta kai tsaye ba don kawai umarnin podman run mai zaman kansa ya yi amfani da pasta cikin nasara. Injin Podman na nesa kuma yana sanya “host” a wurin injin.

Labarai masu alaƙa