links for old versions of Docker for Mac
Docker provides download links in release note. They promised that
(we) will also include download links in release notes for future releases.
Note:
| async def main(): | |
| coroutine1 = do_some_work(1) | |
| coroutine2 = do_some_work(2) | |
| coroutine3 = do_some_work(4) | |
| tasks = [ | |
| asyncio.ensure_future(coroutine1), | |
| asyncio.ensure_future(coroutine2), | |
| asyncio.ensure_future(coroutine3) | |
| ] |
Docker provides download links in release note. They promised that
(we) will also include download links in release notes for future releases.
Note:
| # On the host to run the container | |
| docker run --privileged -i -t -v ~/host-folder-to-mount:/root/folder-ro:ro ubuntu | |
| # Inside the container | |
| # Need to create the upper and work dirs inside a tmpfs. | |
| # Otherwise OverlayFS complains about AUFS folders. | |
| mkdir -p /tmp/overlay && \ | |
| mount -t tmpfs tmpfs /tmp/overlay && \ | |
| mkdir -p /tmp/overlay/{upper,work} && \ | |
| mkdir -p /root/folder && \ |
Just plug in your own values for registry and repo/image name.
registry='localhost:5000'
name='my-image'
curl -v -sSL -X DELETE "http://${registry}/v2/${name}/manifests/$(
curl -sSL -I \
-H "Accept: application/vnd.docker.distribution.manifest.v2+json" \| #!/bin/bash | |
| # add the GPG key for the official Docker repository to the system | |
| curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add - | |
| # add the Docker repository to APT sources | |
| sudo add-apt-repository "deb [arch=amd64] https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable" | |
| # update the package database with the Docker packages from the newly added repo | |
| sudo apt-get update |
The official guide for setting up Kubernetes using kubeadm works well for clusters of one architecture. But, the main problem that crops up is the kube-proxy image defaults to the architecture of the master node (where kubeadm was run in the first place).
This causes issues when arm nodes join the cluster, as they will try to execute the amd64 version of kube-proxy, and will fail.
It turns out that the pod running kube-proxy is configured using a DaemonSet. With a small edit to the configuration, it's possible to create multiple DaemonSets—one for each architecture.
Follow the instructions at https://kubernetes.io/docs/setup/independent/create-cluster-kubeadm/ for setting up the master node. I've been using Weave Net as the network plugin; it see
How to install NVIDIA Docker 2 package on Ubuntu and Debian:
If you came to this result (from Google or elsewhere) after realizing that Nvidia-docker's entry on this subject does not result in a working installation, here are the basic steps needed to install this package correctly:
For starters, ensure that you've installed the latest Docker Community edition by following the steps below:
curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add -
sudo apt-key fingerprint 0EBFCD88
sudo add-apt-repository "deb [arch=amd64] https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable"
| gcc -fpic --shared $(python3-config --includes) greetmodule.c -o greet.abi3.so | |
| # can also use $(pkg-config --cflags python-3.5) | |
| # or | |
| # python3 setup.py install --record files.txt --user |