Vyacheslav

Anyone can point to a guide - if I see multicasts from needed devices on each of the interfaces eth0 and tap0 of the same host, but can't forward one...

@troglobit @jp-t Thank you all for a response. I suspect it is oftopic, but perhaps can be converted to some example. So: I tried to affect TTL in a following...

For notes of everyone interested, who would came here. ``` ip link add br0 type bridge ip link set tap0 master br0 ip link set eth0 master br0 ``` POC...

@binithlighting Did you try advise by @re-mscho ?

That's quite confusing You are adding that in the role for the container build, which looks erroneous ``` name: Add a container to a network, leaving existing containers connected docker_network:...

Workaround would be using virtual environment and full sized requirements.txt to freeze the dependencies, like ``` ansible-container==0.9.2 backports.ssl-match-hostname==3.5.0.1 certifi==2018.1.18 chardet==3.0.4 colorama==0.3.9 docker==3.1.1 docker-pycreds==0.2.2 idna==2.6 ipaddress==1.0.19 Jinja2==2.10 MarkupSafe==1.0 PyYAML==3.12 requests==2.18.4 ruamel.ordereddict==0.4.13...

Any update on this ticket? @davidebelloni did you find any workaround at a time being ?

@Ilmn-Ybi Is issue resolved now? Do you have objections for this issue to be closed?

@jochenparm In this specific case, I understand that there were no dumb-init installed inside container. For your scenario issue might be different

It is not linked to ansible-container, but about unix systems in general (most often used base image in docker ) https://docs.docker.com/v17.09/engine/reference/run/#specify-an-init-process Quoting some article: ### Why valid init for containers...