jpetazzo/pipework

Help with configuring DHCP on pipework

loneshaman opened this issue · 4 comments

Hi all,

I'm currently running docker 1.2 on CentOS 7, and have been trying (unsuccessfully) to assign an IP address to a container using DHCP and pipework.

The command i use to start the container is:

docker run --privileged=true -i -t -d --name <container_name> centos /bin/bash

The pipework command is:

pipework eth0 <container_name> dhcp

As soon as I enter this command, I get the response "I do not know how to setup interface eth0".

What am I doing wrong? I'm extremely new to docker, pipework, and network stuff in general, so please forgive my lack of knowledge.

on centos 7 rhe interfaces are different sir

en0 or others, you need to check the default one

On 28/08/2014, at 12:06 pm, loneshaman notifications@github.com wrote:

Hi all,

I'm currently running docker 1.2 on CentOS 7, and have been trying (unsuccessfully) to assign an IP address to a container using DHCP and pipework.

The command i use to start the container is:

docker run --privileged=true -i -t -d --name centos /bin/bash

The pipework command is:

pipework eth0 dhcp

As soon as I enter this command, I get the response "I do not know how to setup interface eth0".

What am I doing wrong? I'm extremely new to docker, pipework, and network stuff in general, so please forgive my lack of knowledge.


Reply to this email directly or view it on GitHub.

I would have assumed that, but an ip addr show command has the ethernet listed as "eth0".

This is coupled with the fact that I get the same error if I try using en0 instead of eth0.

Do you think it's because I'm trying to do this over a wifi connection?

Edit: it appears I was mistaken about how pipework works. I took a look at the bash code and gained some understanding.

However, eth1 (the interface i just created) only has an ipv6 address, and not the ipv4 address I desire. What could be the cause of that?

Can you try with the latest version of pipework? I think there were some fixes related to unavailability of some DHCP clients.

Closing older issues.