onknows's questions

I installed microk8s in a LXD container

snap install microk8s --classic

When I inspect the instance it shows that snap.microk8s.daemon-proxy is not running

root@mk8s1:~# microk8s inspect
Inspecting Certificates
Inspecting services
  Service snap.microk8s.daemon-cluster-agent is running
  Service snap.microk8s.daemon-containerd is running
  Service snap.microk8s.daemon-apiserver is running
  Service snap.microk8s.daemon-apiserver-kicker is running
 FAIL:  Service snap.microk8s.daemon-proxy is not running
For more details look at: sudo journalctl -u snap.microk8s.daemon-proxy
  Service snap.microk8s.daemon-kubelet is running
  Service snap.microk8s.daemon-scheduler is running
  Service snap.microk8s.daemon-controller-manager is running
  Copy service arguments to the final report tarball
Inspecting AppArmor configuration
Gathering system information
  Copy processes list to the final report tarball
  Copy snap list to the final report tarball
  Copy VM name (or none) to the final report tarball
  Copy disk usage information to the final report tarball
  Copy memory usage information to the final report tarball
  Copy server uptime to the final report tarball
  Copy current linux distribution to the final report tarball
  Copy openSSL information to the final report tarball
  Copy network configuration to the final report tarball
Inspecting kubernetes cluster
  Inspect kubernetes cluster

Building the report tarball
  Report tarball is at /var/snap/microk8s/1769/inspection-report-20201110_051804.tar.gz
root@mk8s1:~# 

How should I setup microk8s in LXD container? This is what I did. Create a profile

lxc profile copy default microk8s
cat microk8s.profile | lxc profile edit microk8s

The profile is as follows

name: microk8s
config:
  boot.autostart: "true"
  linux.kernel_modules: ip_vs,ip_vs_rr,ip_vs_wrr,ip_vs_sh,ip_tables,ip6_tables,netlink_diag,nf_nat,overlay,br_netfilter
  raw.lxc: |
    lxc.apparmor.profile=unconfined
    lxc.mount.auto=proc:rw sys:rw cgroup:rw
    lxc.cgroup.devices.allow=a
    lxc.cap.drop=
  security.nesting: "true"
  security.privileged: "true"
description: ""
devices:
  aadisable:
    path: /sys/module/nf_conntrack/parameters/hashsize
    source: /sys/module/nf_conntrack/parameters/hashsize
    type: disk
  aadisable1:
    path: /sys/module/apparmor/parameters/enabled
    source: /dev/null
    type: disk
  aadisable2:
    path: /dev/kmsg
    source: /dev/kmsg
    type: disk

Launch a container mk8s1

lxc launch -p default -p microk8s ubuntu:18.04 mk8s1

In the container run

apt update && apt dist-upgrade -y && apt install squashfuse -y
snap install microk8s --classic

What am I missing here?

Today I noticed a new message when I login to my Ubuntu 18.04 docker container.

This system has been minimized by removing packages and content that are not required on a system that users do not log into.

To restore this content, you can run the 'unminimize' command.

This is however a container that I log into from time to time.

IMHO it is not a very sound strategy to change systems without user consent in this way but that leaving that aside for the moment, how I can prevent Ubuntu from minimizing my systems?

The minimization breaks functionality of my container and the unminimize command ends with an kernel error.

I have a public interface on a Ubuntu 18.04 VM hosted by a provider that uses OpenStack. Now I want to add a second extra interface for the internal network. I'm not sure how to do that.

Using the web interface of the hosting provider I can add the internal network. After I add this I can see the network interface but no IP address is assigned. Reboot also doesn't help here.

So for example ip a shows

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: ens3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether fa:16:3e:e7:0b:19 brd ff:ff:ff:ff:ff:ff
    inet (MY PUBLIC IP)/24 brd 185.110.173.255 scope global dynamic ens3
       valid_lft 84480sec preferred_lft 84480sec
    inet6 fe80::f816:3eff:fee7:b19/64 scope link 
       valid_lft forever preferred_lft forever
3: ens7: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether fa:16:3e:e3:4f:3f brd ff:ff:ff:ff:ff:ff

My public ip shows up but the interface I added gets no IP address.

I added the ens7 interface to /etc/netplan/50-cloud-init.yaml as follows

# This file is generated from information provided by
# the datasource.  Changes to it will not persist across an instance.
# To disable cloud-init's network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
network:
    version: 2
    ethernets:
        ens3:
            dhcp4: true
            match:
                macaddress: fa:16:3e:e7:0b:19
            set-name: ens3
        ens7:
            dhcp4: true
            match:
                macaddress: fa:16:3e:e3:4f:3f
            set-name: ens7

When I run netplan apply my SSH connection is immediately disconnected and I can no longer access the machime from the internet.

When I use the console and run ip a I see exactly the results I expected however. ens3 has the correct public IP and ens7 has the correct private ip.

I also have a Ubuntu 16.04 VM. Using that cloud image I was able to do this by editing /etc/network/interfaces.d/50-cloud-init.cfg and adding

auto eth1
iface eth1 inet dhcp

But now I want to do something similar on Ubuntu 18.04 VM.

Why am I unable to access the machine using SSH from the internet? IP configuration looks okay.

What is the correct way to add a VM to a second internal private network when using an Ubuntu 18.04 cloud image on OpenStack?

BTW, I am using Ubuntu cloud image bionic-server-cloudimg-amd64.img

In Ubuntu 18.04 the workings of /etc/resolv.conf changed again. Tools break as a result. For example OpenShift local cluster depends on this file.

On the internet it is possible to find how this file can be changed under Ubuntu 12.02 relatively easy.

Is there any documentation that describes how this file works and how its contents can be changed?