MapR Sandbox for Hadoop
Get started immediately with Hadoop with the base image of the MapR Distribution for Hadoop available across all Linux flavors supporting Docker. You can pick and choose the right Hadoop packages and leverage Docker to run multiple MapR single node instances on the same machine.
This image uses sparse disk of size 20GB for MapRFS. If you are using a devicemapper backend (default on all Redhat and some Ubuntu Machines) for Docker. Please delete your existing files under /var/lib/docker/devicemapper/devicemapper and start docker service with the following arguments. This is necessary since the default rootfs size is limited to 10G (Warning: This will delete your existing images and containers.)
--storage-opt dm.basesize=30G --storage-opt dm.loopdatasize=200G
Please ignore error message regarding udev connection during the container startup.
Is there any way to override the generated cluster id? It would be nice to only have to do the registration process (to enable NFS) once and then if we need to remove and rerun the cluster we could set the same cluster ID and reapply the same license every time we spin up the container.
I was able to start multiple containers using the image. Any idea, how can I make them work as a cluster?
Tried to run this both with boot2docker and on a ubuntu 14.04 virtual machine. Both times I am getting the error message:
Starting MapR Services...
Failed to configure Disks...
I have started the docker daemon with the parameters described below:
vagrant@vagrant-ubuntu-trusty-64:~$ ps -ef | grep docker
root 871 1 0 19:47 ? 00:00:01 /usr/bin/docker -d --storage-driver=devicemapper --storage-opt dm.basesize=30G --storage-opt dm.loopdatasize=256G
Also I have deleted the contents of /var/lib/docker before installation of the image.
Is there anyway of seeing more logs of what is going wrong on startup?
Any ideas what might be wrong?
I managed to start one container with the image, any idea about how to run a multinode cluster with this image ? DO we have to re-run the disksetup ?
After installing CentOS7 did you edit your /etc/sysconfig/docker?.
It should look like this
OPTIONS=--storage-opt dm.basesize=30G --storage-opt dm.loopdatasize=256G --selinux-enabled
I usually run my containers like this
docker run -it --rm maprtech/mapr-sandbox-base:4.0.1
I've installed a minimal CentOS 7 distribution, i.e. am executing everything on a native linux installation, and used the provided docker version
[user@localhost ~]$ docker version Client version: 1.1.2 Client API version: 1.13 Go version (client): go1.3.3 Git commit (client): d84a070/1.1.2 Server version: 1.1.2 Server API version: 1.13 Go version (server): go1.3.3 Git commit (server): d84a070/1.1.2
Still, no success, that is
$ docker pull maprtech/mapr-sandbox-base (...wait...) $ docker run maprtech/mapr-sandbox-base Starting MapR Services... ........................................................................................................................Failed to start CLDB...
Could anyone who actually has used this Dockerfile just write a short ping such that I am able to reproduce the steps?
did anyone were actually able to start this image using boot2docker (instead of using a native client under some flavor of linux)?
As stated in the documentation, I removed the aforementioned directory, unfortunately without much success. I think the problem has something to do with using boot2docker on a vm instead of a native docker client. I'll install some linux in a virtual machine and try it there.
If I have any new information, I'll post them here.
As mentioned in the Information tab here: https://registry.hub.docker.com/u/maprtech/mapr-sandbox-base Have you removed the contents of the /var/lib/docker directory. This is necessary since docker might have already populated its metadata with 10gb root aufs from your initial docker runs. This action will remove all containers and images present so far.
thanks for your comment. Nevertheless, adding EXTRA_ARGS="--storage-opt dm.basesize=30G --storage-opt dm.loopdatasize=200G" in /var/lib/docker/profile did not help:
$ docker run maprtech/mapr-sandbox-base Starting MapR Services... Failed to configure Disks...
Using boot2docker ssh I see that the docker service is started with the aforementioned arguments in EXTRA_ARGS.
Any other ideas or hints?
MapR docker images require Device Mapper support, since we need DirectIO to the disks.
With boot2docker, You will need to pass additional arguments to the docker server as described here
Please add to the EXTRA_ARGS="--storage-opt dm.basesize=30G --storage-opt dm.loopdatasize=200G"