Explore >> Select a destination
|
You are here 
|
ariadne.space | ||
| | | | |
blog.simos.info
|
|
| | | | | In the previous post, we saw how to build distrobuilder, then use it to create a LXD container image for Ubuntu. We used one of the existing configuration files for an Ubuntu container image. In th... | |
| | | | |
ops.tips
|
|
| | | | | Yet another blog post on how to create a virtual network that connects network namespaces using a brdige, veth pairs and iptables. | |
| | | | |
blog.mbrt.dev
|
|
| | | | | Over the last year, at work I had multiple chances to debug how containers work. Recently we had to solve some networking problems a customer had with Kubernetes, and I decided I wanted to know more. Once the problem was solved, I spent more time on investigating what is actually going on under the hood. After seeing the wonderful Eric Chiang and Laurent Bernaille talks, and reading through the very informative posts by Lizzie Dixon and Julia Evans (that I really really recommend), I got enough informati... | |
| | | | |
willhaley.com
|
|
| | | After following DigitalOcean's guide for upgrading to Ubuntu Xenial I hit a snag. DNS was broken. I do not see this as a fault of DigitalOcean, but more likely an issue with Ubuntu. Update: 2017-06-27 As U?ur Çetin mentions in the comments below, there is a simpler fix for this. Find the IP address of your mirror and create an /etc/hosts entry for it. Then simply run apt upgrade. Done! Once resolvconf is working properly again, you should be able to comment out or remove the /etc/hosts entry you created for the mirror. | ||
