like Window or OSX, docker-machine is used start linux env, but make is not installed.
I have a Makefile to pull/build/start docker, could not run. how to solve this?
The boot2docker VM is based on Tiny Core Linux, to install a package use tce-load:
docker-machine ssh <profile>
tce-load -wi make
To search for packages you can use the interactive tce tool.
Related
Via nix I have a number of docker executables installed on my local machine.
Here is an example:
/nix/store/dbq6mzbsgwv1rnzc52qjbaf33gsfn51z-docker-19.03.4/bin/docker
/nix/store/dbq6mzbsgwv1rnzc52qjbaf33gsfn51z-docker-19.03.4/libexec/docker
/nix/store/dbq6mzbsgwv1rnzc52qjbaf33gsfn51z-docker-19.03.4/libexec/docker/docker
/nix/store/dbq6mzbsgwv1rnzc52qjbaf33gsfn51z-docker-19.03.4/share/bash-completion/completions/docker
/nix/store/fhhly0rgbygghhfmwmdkacrh6cvg6hvg-user-environment/bin/docker
/nix/store/fhhly0rgbygghhfmwmdkacrh6cvg6hvg-user-environment/libexec/docker
/nix/store/fhhly0rgbygghhfmwmdkacrh6cvg6hvg-user-environment/share/bash-completion/completions/docker
I want to able to reuse the docker installed by nix for my dev work. One of the reasons is that the inhouse toolchain relies on a particular version of docker. If I install Docker for Mac I will run into runtime exception.
Is there neat nix command line trick such I can get the path to the highest version of docker? e.g. in the example above I want to use the docker executable under dbq6mzbsgwv1rnzc52qjbaf33gsfn51z-docker-19.03.4. Ideally, I would like to use something like $(nix find-path docker)/bin/docker to invoke the 19.03.04 docker.
I tried nix run docker or nix dump-path docker but of course they are not the right subcommands.
I want to avoid maintaining another BASH variable to hold a hardcoded path to 19.03.04 docker, because my project might upgrade the docker runtimes from time to time.
I started Docker and am now following the tutorial, but for all I know I couldn't run the docker-machine command on OS X.
The documentation states that you run the following command to create a local virtual machine:
docker-machine create --driver virtualbox manager
However, this command doesn't work in OS X (11.6), with the following error:
Running pre-create checks...
Error with pre-create check: "VBoxManage not found. Make sure VirtualBox is installed and VBoxManage is in the path"
I tried to install the virtualbox; however, another page clearly states that you must not install it on your local machine:
VirtualBox prior to version 4.3.30 must NOT be installed (it is incompatible with Docker for Mac)
Note: If your system does not satisfy these requirements, you can install Docker Toolbox, which uses Oracle VirtualBox instead of HyperKit.
So I only installed Docker for Mac and not virtualbox. So what am I missing here? The example page says you can run the tutorial on OS X, so I wonder how I can proceed...
You can follow along and run this example using Docker for Mac, Docker for Windows or Docker for Linux.
I had the same issue today and resolved it by installing VirtualBox as an additional step after installing Docker for Mac (I did so with brew install --cask virtualbox)
I don't recall having to do the extra install previously, but maybe I already had VirtualBox already installed because of another tool (like Vagrant). Anyway, this is explained in the Docker Machine documentation:
If you are using Docker for Mac
Docker for Mac uses HyperKit, a lightweight macOS virtualization
solution built on top of the Hypervisor.framework in macOS 10.10
Yosemite and higher.
Currently, there is no docker-machine create driver for HyperKit, so
you will use virtualbox driver to create local machines. (See the
Docker Machine driver for Oracle VirtualBox.) Note that you can run
both HyperKit and Oracle VirtualBox on the same system. To learn more,
see Docker for Mac vs. Docker Toolbox.
Make sure you have the latest VirtualBox correctly installed on your system (either as part of an earlier Toolbox install, or manual
install).
I had the same issue. At the same spot ;-)
For me the xhyve driver, available from https://github.com/zchee/docker-machine-driver-xhyve, worked.
In short:
brew install docker-machine-driver-xhyve
You get a notice some links need to be created manually, so copy those and execute
sudo chown root:wheel /usr/local/opt/docker-machine-driver-xhyve/bin/docker-machine-driver-xhyve
sudo chown root:wheel /usr/local/opt/docker-machine-driver-xhyve/bin/docker-machine-driver-xhyve
Create:
docker-machine create --driver xhyve manager
Without VirtualBox. Im using OS X 10.11.6, too.
After updating my docker docker-machine command stopper working on my mac terminal.
So found after updating my docker I'll have to reinstall docker-machine CLI just to get the latest version.
Updated docker-machine to latest one using the command below helped me making docker-machine command working again.
base=https://github.com/docker/machine/releases/download/v0.16.0 &&
curl -L $base/docker-machine-$(uname -s)-$(uname -m) >/usr/local/bin/docker-
machine &&
chmod +x /usr/local/bin/docker-machine
See Docs (https://docs.docker.com/machine/install-machine/#install-machine-directly)
I have installed the new Docker Toolbox application for the Mac using both the graphical installer (the official one) and brew cask install.
In both cases, the Virtual Machine is correctly created, but something seems to be wrong in the environment because when I try to execute docker-machine on the command line, it fails like this:
$ docker-machine env default
open /Users/adeynack/.docker/machine/machines/default/ca.pem: no such file or directory
When I try Kitematics, it fails like this:
I tried Delete VM and retry setup, without success. Any insight or idea is welcome here.
EDIT: I am already using the test build 5.0.3 of VirtualBox.
This may have been caused by an issue with Virtualbox. The issue has been fixed with the latest testbuild for virtualbox here: Virtualbox Test build.
You have to uninstall your current version of Virtual Box and install the test build.
Edit
You may need to create a new docker machine.
Create a new docker machine:
docker-machine create --driver virtualbox dev
Next, start the dev environment:
docker-machine env dev
Set up the environment for the dev machine:
eval "$(docker-machine env dev)"
This worked for me:
docker-machine regenerate-certs default
docker-machine restart default
I'm new to Docker...
From my understanding, Docker is only compatible with Linux, is it possible to run docker for development purposes on a Mac?
I installed virtualbox using homebrew and have tried to create a virtualbox instance. I installed docker, but am having trouble getting my mac to communicate with the vm docker instance. My end goal is to get a locally debuggable instance of tomcat running on the docker container.
Any help or tips would be helpful.
Information:
Because Docker only runs on Linux you will need to install some kind of virtual instance on your local machine. An easy and popular way to do that is to install
Boot2docker and VirtualBox. VirtualBox is a dependency of Boot2docker. You can download, setup and install the latest versions from their websites or if you are using Homebrew, as you mentioned, you can quickly get the working binaries both in one step.
After installing boot2docker, you're ready to use Boot2docker to create a Tomcat Container. You can find a pre-configured tomcat image by searching Docker's community repository, docker hub registry.
Notes:
Each time you execute the docker run command a new container is created.
The VM running Docker requires a ssh private/public encryption key handshake to connect to. If you follow my steps below, one will be generated for you.
Steps to Setup Tomcat using the tomcat image:
Open Terminal and run this command: brew install boot2docker
Create a new Boot2Docker VM instance using the init command: boot2docker init
Run this command in Terminal to forward local ports to the vm:
for i in {10000..10999}; do VBoxManage modifyvm "boot2docker-vm" --natpf1 "tcp-port$i,tcp,,$i,,$i”; VBoxManage modifyvm "boot2docker-vm" --natpf1 "udp-port$i,udp,,$i,,$i";done
Start the boot2docker daemon: boot2docker start or boot2docker up
After starting docker, copy the exports that are displayed from the previous command to your clipboard
Edit your bash profile file ~/.bash_profile (or if you are using zsh, edit the resource configuration file ~/.zshrc) with a text editor (I prefer using Sublime text): subl .zshrc *note: this will permanently save the docker env variables.
Paste the exports into that file and save
Execute the source command on the file: source .zshrc
Pull the latest tomcat image to create a container and start tomcat: docker run -it --rm -p 10080:8080 tomcat:8.0 *note: this will forward your local 10080 port to the vm's 8080 port.
Go to http://localhost:10080, you should see the tomcat start page!
Useful Docker commands:
$ boot2docker status
$ docker version
$ docker ps #shows running containers
$ docker ps -a # shows all containers
$ docker exec -it NAME /bin/bash #to start a bash session on the container. -i = interactive, -t = tty
External Resources:
https://docs.docker.com/installation/mac/#installation
https://registry.hub.docker.com/_/tomcat/
Most people use boot2docker to run on Macs. You may also want to take a look at Kitematic, which gives you a GUI to play with.
Finally, the future is probably to use docker machine, which can provision a VM for you.
Docker requires Linux Kernel features, hence it cannot be run natively on OSX.
See instead Boot2Docker. This link gives you instructions on how to get going.
I'm in boot2docker. I'm not entirely sure I understand it completely, but it seems to be needed for a project I'm on.
I've ssh'd in, and I tried to do a make on our project, but I got
make: not found
Then I tried a:
apt-get install make
And got
apt-get: not found
Tried googling, but couldn't find anything about that, or any package manager.
Any suggestions on how to install anything in boot2docker?
EDIT:
When I asked this I misunderstood how boot2docker and docker worked hand in hand. There is actually a package manager (tce-load) that allows install of packages, but really, it shouldn't be used and anything involving a project using docker should be using a docker container within boot2docker that has the build tools inside of that. Although I did find tce-load useful installing nano, since I'm not a fan of vi and that's occationaly useful.
Seems boot2docker uses Tiny Linux which has its own package manager called "tce-load". There's a list of packages for it here:
http://distro.ibiblio.org/tinycorelinux/tcz_2x.html
There's everything that's needed to make or whatever located there.
You should not be installing anything on the boot2docker vm as that gets deleted and reset often. You should install any tools inside a docker container running on the boot2docker vm.
Only linux can run docker so when running on osx or windows you must use boot2docker. boot2docker is just running a linux vm that has docker installed. Once you are using boot2docker you use docker like you would normally.
The boot2docker vm is not where you should be installing things, what you should be doing is running a container that has the programs you need installed. This can be accomplished by finding a useful image from the docker registry or by making your own docker image.