By default, your containers are accessible only from the host. For serious use you will want to expose some containers to the outside world. There are various ways of doing this. Currently I have settled on the following,
Port Forwarding using Static IPs with IP Tables - allows you to leverage your host's IP address (assuming it is public).
macvlan with Additional IP - allows you to have, a dedicated network interfaces (to the outside world) but actually only use one real physical network card. Unlike using a bridge this will not have the cpu overhead and need for your network card to work in promiscuous mode. This article builds on the work done in the introductory LXC article.
I actually use multiple techniques together.
Make sure to change the password or better remove the default ubuntu account generated by the lxc creation script before making the container accessible to the Internet.
This will get better over time, ie compared to Solaris where you just tell the container to use a public IP address and the macvlan or bridging is done for you.
Port Forwarding using IP Tables
You might want to use one IP Address on the host and then map specific ports out from the containers. As a pre-requisite you will need to setup Static LXC Assigned IP address.
There are a number of ways to do this but I favour iptables.
In this example we setup Apache which runs on port 80 in the container which has been assigned the static IP 10.0.3.10.
Make sure the host is not listening on port 80,
Next determine your hosts network card name associated with the hosts IP address,
In this case, I know my host's public IP6 address (put reference of how to convert to ip4 or reverse lookup on dns IP6 address) is fe80::20d:3aff:fe02:e68a/64 and see it as the first entry. This let's us know the network card name is eth0. In Ubuntu it will normally be eth0 or ens33.
While on the host issue these commands, (TBD, look at making own named chain to distinguish the rules)
Now traffic on port 80 on the host will be forwarded to port 80 in the container IP specified. You can see your rules, (note I got to review output again on a clean machine).
You might want to delete the rule. Again, note this is not persistent upon reboot. Execute the exact same command to add, but change -A to -D,
If you test the rule and like it. Make it persistent,
Going further you can actually remap ports too. In this example, I map port 23 on the host server to the 22 on the container,
bridge with Additional IP Address
How to adjust LXD,
Also rever to my own article on bridge networking.
macvlan with Additional IP Address
Here's the Use Case,
The most viable options, I understand are using bridge or a dedicated vlan.
With macvlan you configure the container to directly use the public IP address without the overhead of changing the network card to promiscuous mode and have a lower CPU overhead. Once setup the macvlan gets it's own MAC address. This only works if there are no restrictions on the network which set's static IPs based on the hosts' MAC address. Usually this is only the case with the initial primary IP provided by the hosting company.
The containers can reach the network and each other, but not the host. Even though the host may be on the same network. This is by design of macvlan. The container network cards (Sub-interfaces) on the same host (parent) cannot communicate with each other. ALL frames from sub-interfaces are forward out through the parent interface. Even physcial switches that reflect the frames back in will get dropped.
If you had previously assigned a static IP to the container using /etc/lxc/dnsmasq.conf make sure to remove the entry (I believe you also need to restart the host).
You must have,
- 1 macvlan mapped to 1 container interface
- each interface must have different static IP addresses
macvlan mac address
The first thing to do is to create a mac address for the macvlan interface we will create on the host.
According to this article the Second bit of the most significant Byte indicates if the MAC address is locally or universally administered. (I think locally is better for public facing so you do not collide with other mac addresses). When generating MAC addresses for macvlan, this bit should be set to '1', indicating it is locally administered. As such, translated to a mac address any of these numbers are locally managed and you will not need to worry about colliding with the larger Internet,
Right now I have not read enough to describe the math, but for now, use the hellion website to generate a Random Locally Administered Unicast MAC Address. In this example, I selected 8a:38:2a:cc:d7:aa because the last aa is easy to search on.
You can not use the same MAC interface on multiple containers on the same host. Otherwise, you will not be able to start you container and receive the error message about your interface already being in use.
Command Line macvlan
You can use the command line inside your container to quickly create a macvlan and test, but it will disappear after reboot,
Create a Permanent macvlan on the Host
Add to the bottom of the /etc/network/interfaces file of the host,
Notice that the MAC address is locally generated. The mavclan interface is actually not directly used and the MAC address will not actually register with anything. I am uncertain if it matters, so I have put in a static rather than generated MAC address out of preference (I don't like the idea of it changing on every boot). Not using a MAC address at all here might work too. If you the reader has time, let me know.
This macvlan0 is a placeholder on the host that will be used by a container interface. I have only purchased one additional static IP address so not all scenarios are tested.
If somebody gets to step 2 in below chart, please fill out for me. Otherwise, I'll try myself using my home network which is not exactly the same thing.
|1||mvlan0||connect to mvlan0 with static-IP-1 with container2 off||connect to mvlan0 with static-IP-1 with container1 off||success|
|2||mvlan0||connect to mvlan0 with static-IP-1 with container2 on||connect to mvlan0 with static-IP-2 with container1 on||Not sure... I need to buy another static IP to test|
Scenario 1 basically shows that a macvlan in the host may be used by multiple containers as long as only one host is on at a time.
Scenario 2 may or may not in which case we would want to create a scenario 3 by adding an additional macvlan mvlan1.
Look at your existing network cards,
Reboot your system to have the change take effect. Review your network card list,
Notice mvlan0 is present with the hardware address you specified.
Connect Container to macvlan on Host
Now one container may connect to the mvlan0 interface on the host and they will get their IPs directly from the same network connected to the host (if DHCP) or you can assign static IPs inside the container that are reserved for you.
Make the container aware of the mvlan0 by modifying the config file located in /var/lib/lxc/[container]/config. In this example, I named the container web so the location will be /var/lib/lxc/web/config.
We will be adding a network card for the container. First step is to use the hellion website to generate a Random Locally Administered Unicast MAC Address. Then, modify the config file by adding a network card for the container.
This tells the container to use the macvlan network interface mvlan0 which we created in the host and in turn map it to the container's eth0 interface.
I generated a new MAC address here by creating a temporary container, copying the mac address and then destroying the container. The LXC mac address looks like a universally administered number which worked with my hosting provider. For some reason the locally administered did not appear to work (I'll need to do one more test again when time permits to confirm).
There is a command line way of generating an LXC mac address this (actually documented somewhere in this LXC documentation) but I have not had a chance to try it.
Also, note that I kept the automatically generated interface eth0 and renamed it eth1. This will allow the container to communicate to other containers who are using the LXC DHCP provided IP address in the internal LXC network.
There is probably a way to setup the static ip address here in this config file for the container. I am pretty sure I saw an option. However, in the vein of individual container control, I would rather set that at the container level using steps outlined below.
Next, modify the interfaces file within the container to your selected static IP address. I find the fastest is from within the Host OS using root, /var/lib/lxc/<container name>/rootfs/etc/network/interfaces which in this case would be, /var/lib/lxc/web/rootfs/etc/network/interfaces,
Above we now have two interfaces. The static interface is the public IP address purchased called eth0 and second is the internal LXC assigned address. The other entries can be obtained from Add Additional IP Addresses to Ubuntu Server.
Make sure to check your dnsmasq and make modifications accordingly. Using the example since we modified a container that was already using dnsmasq we needed to change the original /etc/lxc/dnsmasq.conf,
The new file looks like this,
Because the container called "web" now has two interfaces. 1 static, 1 we still want to assign through dnsmasq. In order for dnsmasq to know which interface to use you, must now specify by using the mac address contained in the /var/lib/lxc/[container]/config.
You need to shutdown containers and restart the host or flush the DNS Masq,
So first shutdown all your containers (Aug 2016, there is an issue that lxc-net does not restart unless all containers are shut off). Then restart lxc-net,
The other option is to shutdown all containers and restart the host operating system.
In most cases you will want multiple interfaces. In this example, we built a front-end container called "web", gave it a public IP address using mavlan. In addition, we create an "app" container which has an lxc internal IP address. In order for web and app to communicate, web must have a second interface that also uses an lxc provided internal IP address.
(...draw a diagram here...)
I got this all working, but need to document.
This looks promising... The most prominent user of macvtap interfaces seems to be libvirt/KVM, which allows guests to be connected to macvtap interfaces. Doing so allows for (almost) bridged-like behaviour of guests but without the need to have a real bridge on the host, as a regular ethernet interface can be used as the macvtap's lower device.
Networking LXD More Detail - https://www.flockport.com/lxc-networking-guide/
INotes issue about bridge mode promiscuous mode - http://wiki.alpinelinux.org/wiki/LXC#Creating_a_LXC_container_without_modifying_your_network_interfaces
Getting macvlan working - https://www.flockport.com/lxc-macvlan-networking/
Learning macvlan and good background info - http://backreference.org/2014/03/20/some-notes-on-macvlanmacvtap/
Oracle article on details of container creation - http://docs.oracle.com/cd/E37670_01/E37355/html/ol_config_os_containers.html#ol_setup_fs_containers
Looks to be most comprehensive yet of what I want (multiple network cards with macvlan) - http://containerops.org/2013/11/19/lxc-networking/
How I figured out to create a macvlan - http://cyberiantiger.livejournal.com/24104.html
Not sure I can use comments here... need to investigate if it causes issues.
Generate mac address same way lxc does - http://giantdorks.org/alain/how-to-generate-a-unique-mac-address/
More in depth and discusses outbound NAT so containers can communicate to other container public IPs -http://blog.codeaholics.org/2013/giving-dockerlxc-containers-a-routable-ip-address/
Bridge versus Macvlan - http://hicu.be/bridge-vs-macvlan