Hi Everyone.
I have below trouble.
I start my container with --network-interface option as below:
ExecStart=/usr/bin/systemd-nspawn -M %i.%H --quiet --keep-unit --boot
--link-journal=auto --network-veth *--network-interface=dummy6*
--capability=CAP_NET_RAW --directory=/var/lib/container/%i
On 17.04.2017 11:59, Lennart Poettering wrote:
> On Thu, 13.04.17 16:08, poma (pomidorabelis...@gmail.com) wrote:
>
>> Hello
>>
>> Regaining of the network-interface, as is stated in the manual, ain't
>> happening;
>> man 1 systemd-nspawn
>> ...
>> OPTIONS
>> ...
>> --network-interface=
>>
On Thu, 13.04.17 16:08, poma (pomidorabelis...@gmail.com) wrote:
> Hello
>
> Regaining of the network-interface, as is stated in the manual, ain't
> happening;
> man 1 systemd-nspawn
> ...
> OPTIONS
> ...
> --network-interface=
> Assign the specified network interface to the container.
>
Hello
Regaining of the network-interface, as is stated in the manual, ain't happening;
man 1 systemd-nspawn
...
OPTIONS
...
--network-interface=
Assign the specified network interface to the container.
This will remove the specified interface from the calling namespace and
place it in the
Hi,
if i understnd this correct, the network interface names (veth and
macvlan) are created with the frist 11 Caracters from the
Containername (Machinename).
Now if you use similar names for conatiners, like
com.$company.$devision.$name1
com.$company.$devision.$name2
On Thu, 18.06.15 18:27, Florian Koch (florian.koch1...@gmail.com) wrote:
Hi,
if i understnd this correct, the network interface names (veth and
macvlan) are created with the frist 11 Caracters from the
Containername (Machinename).
IFNAMSIZ emposed by the Linux kernel is 16, and we need
