VNC server installation on Linux Mint running the Mate desktop environment

VNC server on Linux Mint Mate desktop

Introduction

The installation of a VNC server on Linux Mint -running the Mate desktop environment- can be accomplished by following this step-by-step guide. The procedure below is scoped to run the vnc server on demand, it is, only when required.

Procedure

First thing anyone should do is to trigger an update of the packages from the corresponding repositories. To accomplish this, simply run:

sudo apt-get update

I would say it should be good to upgrade the versionof the installed packages by running:

Read more

NFS 4.1 support on Azure File Shares

NFS

The NFS 4.1 support on Azure File Shares -in public preview- is a fully POSIX-compliant offer ideal for workloads that require POSIX-compliant file shares, case sensitivity, or UNIX style permissions (UID/GID).

The NFS 4.1 support -in preview– on Azure File Shares is available in a number of Azure regions. You may find additional information about NFS 4.1 support on Azure File Shares in these articles “How to create an NFS share” and “Azure file share protocols“.

Installation of kubernetes on Azure virtual machines

kubernetes installation guide

This is a demo guide of how to install kubernetes master and worker nodes on Microsoft Azure standalone virtual machines.

This guide is not intended as a solution for production purposes.

Pre-requisites

This guide assumes that you have a Microsoft Azure account and that you installed the Azure CLI and you are logged in to the respective subscription in Azure.

First steps

To create a resource group:

az group create -n rg_k8sdemo --location eastus2 --tags Purpose=Education

To create a VNET:

az network vnet create \
--resource-group rg_k8sdemo \
--name vnet-k8s-101519 \
--address-prefix 10.0.0.0/16 \
--subnet-name subnet-k8s-101519 \
--subnet-prefix 10.0.0.0/24

To create a virtual machine (as master):

az vm create \
--location eastus2 \
--size Standard_B1ms \
--resource-group rg_k8sdemo \
--image UbuntuLTS \
--computer-name my-k8s-master-00 \
--name k8s-101519-master-00 \
--vnet-name vnet-k8s-101519 \
--subnet subnet-k8s-101519 \
--storage-sku Standard_LRS \
--ssh-key-values .ssh/id_rsa.pub \
--tags role=master

Read more

Basic kubernetes commands to investigate an issue

There are many usage cases of kubernetes and, hence, very distinct support scenarios when it deals to supporting a kubernetes issue. In my experience, I would call the following basic kubernetes commands to investigate an issue, as the most useful -and necessary- to accompany any kubernetes issue report.

Basic kubernetes commands to investigate an issue
kubectl version
kubectl cluster-info
kubectl get nodes -o wide
kubectl get pods --all-namespaces -o wide
kubectl get deployments --all-namespaces
kubectl get svc --all-namespaces -o wide

On the same time, I would include these couple of Docker commands:

docker -v
docker ps

To speed up any kubernetes troubleshooting, I’d recommend to provide the output of those commands in TXT format, rather than taking a screenshot.

Do you have any other experienced-based basic kubernetes command you would add to this list? Please share in the comments section.

Definitive guide to: The following packages have been kept back

In virtually every installation of Debian -or derivative- it will happen that at some point during software management one will be prompted this message: The following packages have been kept back Let’s provide an example to make it clear.

Example

First, you ran:

apt-get update

and everything was fine. We can affirm the command reported a 0 exit code.

After this you ran:

sudo apt-get upgrade

if your OS‘ software gets updated often and if it is updated at the time of running the upgrade command the output will be like this:

[email protected]:~$ sudo apt-get upgrade
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
  cinnamon-screensaver
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.

… and there is the weird message: The following packages have been kept back.

Read more