OpenWRT in docker

AFAIK OpenWRT isn't intended to be run in a Docker container... What kind of setup have you got there?

I have never had to use a config file for Docker networking...

Kubernetes is overkill if you want something simple. There's a steep learning curve. Also I'm not sure it's the right thing for OpenWRT.
 
newby_investor said:
AFAIK OpenWRT isn't intended to be run in a Docker container... What kind of setup have you got there?

I have never had to use a config file for Docker networking...

Kubernetes is overkill if you want something simple. There's a steep learning curve. Also I'm not sure it's the right thing for OpenWRT.
Click to expand...

So the solution works OK with virtualization platforms such as vmware/xen. However, as instance count goes up the virtualization platform starts hitting performance problems.
I've tried a number of times to make OpernWRT work with nspawn as an alternative. Had some success but can't seem to make it headless. I then came across the docker version.
 
r00igev@@r said:
docker - unable to make docker work with dhcp
Click to expand...
You can create a Mac-vlan to give the instances unrestricted network access in their network segment,stick a DHCP server in there or have docker hand out IPs in the range
docs.docker.com

Macvlan network driver

All about using Macvlan to make your containers appear like physical machines on the network
docs.docker.com docs.docker.com
(This is for when you need to attach IPs to services rather than reverse proxy them into the bubble)
 
I'm trying to understand what your use case is here.

Docker kind of manages its own networking. Why do you need openwrt? If you want to route traffic between virtual hosts, why don't you use a more traditional Linux routing thing like pfsense?
 
PsyWulf said:
You can create a Mac-vlan to give the instances unrestricted network access in their network segment,stick a DHCP server in there or have docker hand out IPs in the range
docs.docker.com

Macvlan network driver

All about using Macvlan to make your containers appear like physical machines on the network
docs.docker.com docs.docker.com
(This is for when you need to attach IPs to services rather than reverse proxy them into the bubble)
Click to expand...
Yes, nspawn works perfectly with dhcp but docker requires the range to be configured on the command line. Scripting an nspawn instance is easier.
 
newby_investor said:
I'm trying to understand what your use case is here.

Docker kind of manages its own networking. Why do you need openwrt? If you want to route traffic between virtual hosts, why don't you use a more traditional Linux routing thing like pfsense?
Click to expand...
pfsense works in a stock virtualization environment but it doesn't really scale in performance and resources. I used a pure debian image in a nspawn container with firewalld and the performance is excellent and it scales. Just no user GUI for it! I was hoping that OpenWRT would do the same and it has a web based management ability by default. Now if only debian firewalld had the same thing! Cockpit comes close but you still need to do most of the config via the cli.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X