There are numerous reasons you may need to use multiple SSH keys for accessing GitHub and BitBucket
You may use the same computer for work and personal development and need to separate your work.
When acting as a consultant, it is common to have multiple GitHub and/or BitBucket accounts depending on which client you may be working for.
You may have different projects you're working on where you would like to segregate your access.
| minikube stop; minikube delete && | |
| docker stop $(docker ps -aq) && | |
| rm -rf ~/.kube ~/.minikube && | |
| sudo rm -rf /usr/local/bin/localkube /usr/local/bin/minikube && | |
| launchctl stop '*kubelet*.mount' && | |
| launchctl stop localkube.service && | |
| launchctl disable localkube.service && | |
| sudo rm -rf /etc/kubernetes/ && | |
| docker system prune -af --volumes |
| pct create <id> /var/lib/vz/template/cache/centos-7-default_20170504_amd64.tar.xz \ | |
| -arch amd64 \ | |
| -ostype <centos|ubuntu|etc> \ | |
| -hostname <hostname> \ | |
| -cores <cores> \ | |
| -memory <memory(MB)> \ | |
| -swap <swap(MB)> \ | |
| -storage local-lvm \ | |
| -password \ | |
| -net0 name=eth0,bridge=<bridge>,gw=<gateway>,ip=<cidr>,type=veth &&\ |
Jon Warbrick, July 2014, V3.2 (for Ansible 1.7)
First one found from of
