If you try to install Docker on Ubuntu Server v16.10 (Yakkety) using the installation script provided by Docker, this will result in the error “E: Unable to locate package docker-engine”. My solution was to change the repository it was grabbing from Yakkety to the LTS (Long Term Support) version 16.04 – Xenial.
- Update package info and install certificates
sudo apt-get update
sudo apt-get install apt-transport-https ca-certificates
- Install the recommended pre-requisites
sudo apt-get install linux-image-extra-$(uname -r) linux-image-extra-virtual
- You can skip running the installation script, as this will result in the error “E: Unable to locate package docker-engine”.
wget -qO- https://get.docker.com/ | sh
- Update the docker.list file to force it to pull from the other repo. You can verify it updated correctly by reading the file to the screen. Only the one line should be in the file.
echo "deb https://apt.dockerproject.org/repo ubuntu-xenial main" | sudo tee /etc/apt/sources.list.d/docker.list
- Update package info again and then install Docker
sudo apt-get update sudo apt-get install -y -q docker-engine
- Start Docker and verify that it is running
sudo service docker start
sudo service docker status
- Run a test image
sudo docker run hello-world
- Give your non-root user permissions to run docker. Change “myusername” to your user.
sudo usermod -aG docker myusername
There is a ton of good information out there about Docker, but I wanted to provide you with a more consolidated walk through that gets you started from ground zero. In the spirit of virtualization, isolation, and containerization, this guide is going to leverage the open source Photon OS from VMware. Let’s get started!
- Go to vmware.github.io/photon/ and download the appropriate ISO or OVA for your environment.
- For the purposes of this guide, I deployed the Minimal hw v11 OVA into my vSphere cluster, but I have successfully done the same thing within Workstation.
- You can also build a VM from scratch (1 vCPU, 384MB RAM, 8GB Disk minimum) and use the ISO (which will also allow you to deploy the “Full Version.”) Note that the OVA will deploy a VM with 1 vCPU, 2GB RAM, and 16GB Disk.
- Once deployed and powered on, either use the hypervisor’s console or SSH into the VM, then login with “root” and “changeme”
- The first time you log in, you will be required to change the password.
- Surprisingly, Docker isn’t running, so start Docker, then verify it is working, by running:
systemctl start docker
The “docker ps” command lists running containers, which we don’t have yet, but will error out if Docker isn’t running properly. You will see an output like “CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES” if Docker is working.
Continue reading Getting Started with Docker & VMware Photon OS
If you are using Nexenta or Nexenta CE (Community Edition) v4.04 you may have noticed that within VMware, the Hardware Acceleration (VAAI) status is listed as Unknown.
Nexenta v4.04 and possibly some other versions ship with VAAI in a default / disabled state. Follow these steps to Enable Hardware Acceleration:
- Download and extract the Nexenta vaaictl python script from the following link: http://downloads.nexenta.com/cdn/NexentaStor/utilities/vaaictl.zip
- If the link doesn’t work, I have pasted the output of the file below.)
- Copy the vaaictl file to your Nexenta box to /tmp
- Using WinSCP with windows via SFTP works well for this.
- SSH into your Nexenta box using PuTTY or another tool. Enter Expert mode by running:
option expert_mode =1
- Run the following commands to check the status of VAAI:
chmod 555 ./vaaictl
- Output: “Current status is defaulted.”
- To enable VAAI, run the following:
sudo ./vaaictl --enable
- Output: “Changing from defaulted to enable”
- You can now re-check the status of VAAI:
- Output: “Current status is enabled.”
Continue reading Nexenta VMware Hardware Acceleration Unknown – Solved