You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Seems we can create a new network for the whole plan and assign it to the containers . 'multihost' plugin can inspect the IP and fill the /etc/hosts properly.
Short experiment: podman network create --disable-dns FOO_NAME followed by podman run --net FOO_NAME.
The inspect should look into {{json .NetworkSettings.Networks.FOO_NAME.IPAddress}}
On my machine (fedora 37) I didn't need to specify subnet when creating network however without --disable-dns containers where not able to resolve url for fedora repositories.
The text was updated successfully, but these errors were encountered:
Currently they are not able to do so. @kkaarreell pointed out his solution in https://github.com/RedHat-SP-Security/keylime-tests/blob/main/container/functional/keylime_verifier_registrar_container-basic-attestation/test.sh#L26 and https://github.com/RedHat-SP-Security/keylime-tests/blob/main/Library/test-helpers/lib.sh#L1910
Seems we can create a new network for the whole plan and assign it to the containers . 'multihost' plugin can inspect the IP and fill the /etc/hosts properly.
Short experiment:
podman network create --disable-dns FOO_NAME
followed bypodman run --net FOO_NAME
.The inspect should look into
{{json .NetworkSettings.Networks.FOO_NAME.IPAddress}}
On my machine (fedora 37) I didn't need to specify subnet when creating network however without
--disable-dns
containers where not able to resolve url for fedora repositories.The text was updated successfully, but these errors were encountered: