To install Debian 11.0(bullseye), download any of the following images (all i386 and amd64CD/DVD images can be used on USB sticks too):
Step 4: Post Installation & Configuring of Wine on Debian 11 Bullseye. With Wine installed successfully on your Debian 11 system, let’s now see the configurations to make on it. Launch wine from your terminal as shown. Install the Wine Mono environment. Also, install the Wine Gecko environment. Install Docker Engine. This procedure works for Debian on x8664 / amd64, armhf, arm64, and Raspbian. Update the apt package index, and install the latest version of Docker Engine and containerd, or go to the next step to install a specific version: $ sudo apt-get update $ sudo apt-get install docker-ce docker-ce-cli containerd.io.
netinst CD image (generally 150-280 MB)
full CD sets
full DVD sets
CD (via BitTorrent)
DVD (via BitTorrent)
CD (via jigdo)
DVD (via jigdo)
Blu-ray (via jigdo)
other images (netboot, flexible usb stick, etc.)
If any of the hardware in your system requires non-free firmware to beloaded with the device driver, you can use one of thetarballs of common firmware packages or download an unofficial image including these non-free firmwares. Instructions how to use the tarballsand general information about loading firmware during an installation canbe found in the Installation Guide.
netinst (generally 240-290 MB) non-freeCD images with firmware
If you read only one document before installing, read ourInstallation Howto, a quickwalkthrough of the installation process. Other useful documentation includes:
This is a list of known problems in the installer shipped withDebian 11.0. If you have experienced a probleminstalling Debian and do not see your problem listed here, please send us aninstallation reportdescribing the problem orcheck the wikifor other known problems.
Improved versions of the installation system are being developedfor the next Debian release, and can also be used to install bullseye.For details, seethe Debian-Installer projectpage.
Five years ago I wrote this blog entry talking about KVM, at that time I needed to run Microsft Windows 7 VM to make some tests for my work.
This time I need to make a lab with a couple of VMs to run a Kubernetes cluster in my laptop and I’ve decided to use KVM to create the required infrastructure.
First of all let’s check if we have enable virtualization at BIOS level we can check it running:
As it’s shown in log virtualization needs to be enabled entering in BIOS menu to enable VT-X options, with this change in the next boot it can be found in boot log:
In addition is also required to check if our CPU support hardware virtualization, we are going to include encryption check running this command:
Reviewing information from our CPU from /proc/cpuinfo we can find these flags:
lm – this flag means your system has a 64 bit CPU (Intel or AMD)
vmx – Intel VT-x, virtualization support
aes – AES/AES-NI advanced encryption support
Let’s install all needed packages:
virtinst package would be required if you want to use virt-install command.
To connect to local libvirt:
We are going to use libvirt which is an open-source API, daemon and management tool for managing platform virtualization to make easier manager our KVM environment.
As a requirement we need that our VMs are connected between them because they are going be part of a cluster so let’s setup a bridged networking :
In my case
enp0s31f6 is the host ethernet interface to be connected to the bridge you can find yours using this command:
We’re setting up our bridge using a separated file located here /etc/network/interfaces.d/br0:
Let’s check our new configuration restarting network-manager service (you should check if your network set up is controlled by Network Manager):
Edit /etc/sysctl.conf file adding the following options:
A reboot is required, although let’s check bridge setup within KVM:
To get br0 MAC address run:
If we want to modify some information to setup the range in DHCP it can be done like that:
Some of the most commands to work with VMs:
With our bridge correctly configured we can setup next VM deployments using this flag:
Let’s define a script to create our VM’s (memory, disk and vcpu will depend on your host hardware):
Let’s create our first VM:
In this tutorial I’m not going to describe how to setup a Debian GNU/Linux VM but some minimalrequirements in our case could be:
# swapoff -a && sed -i '/ swap / s/^/#/' /etc/fstab
Once we have our VMs setup it’s time to install kubernetes cluster software steps in MASTER NODE:
Let’s create a Discovery Token CA Hash in the master node to ensure that a worker joins the cluster in a secure way. To generate this hash:
This directory keeps all manifest files: /etc/kubernetes/manifests
Steps in a WORKER NODE:
If your token has expired you should follow these steps:
Let’s check in the master node if we can see the new node added to the cluster (has to be checked in all cluster nodes):
Both master and worker should have these network interfaces you run this command to make a quick check:
Note that if something was wrong during installation process probably the quickest way to fix the problem could be to restart a fresh installation process quickly destroying VM and starting again.
Enjoy your new fresh k8s cluster!
First they ignore you,
then they laugh of you,
then they try to copy you.
Then you change the world.
— Elisabeth Holmes