Question 1

How to attach a Docker container to a physical network interface with pipework?

Accepted Answer

Use commands like 'pipework eth2 $CONTAINERID 192.168.1.2/24' for macvlan or '--direct-phys' for exclusive access. This creates a subinterface on the host, but requires configuring promiscuous mode on virtualized hosts per the README.

Question 2

Pipework vs Docker bridge network: which should I use?

Accepted Answer

Use Docker's native bridge for simple, managed inter-container communication. Pipework is only for complex scenarios Docker doesn't support, like VLANs or direct physical attachments, but it's unmaintained and riskier.

Question 3

Does pipework work with Kubernetes pods?

Accepted Answer

No, pipework is designed for standalone containers and isn't compatible with Kubernetes' network model. Kubernetes uses CNI plugins for networking, making pipework obsolete in such environments.

Question 4

How to set up VLANs for containers using pipework?

Accepted Answer

Specify VLAN IDs with '@VID' in the MAC address parameter, e.g., 'pipework ovsbr0 $CONTAINERID dhcp @10'. Note that this only works with Open vSwitch or physical interfaces, not standard Linux bridges.

Question 5

Is pipework safe to use in production today?

Accepted Answer

No, the README warns it's not maintained and may break with Docker updates. It's best for legacy setups or testing, but avoid it for production due to lack of support and potential incompatibilities.

Question 6

How to run DHCP persistently with pipework to renew leases?

Accepted Answer

Add flags like '-f' for the DHCP client (e.g., 'dhcp:-f') to keep it running, but you must manually manage and kill these processes later, as pipework doesn't handle long-term lease renewal automatically.

Pipework

What is Pipework?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions