eb16b4a782
After a bit of research into [0] and [1], and a bit of experimentation, it seems we can use a partial wild-card expression for these version strings. Let's try this for now. If it works out, we should expand this usage to all the version package numbers, pinning them to their epic:upstream-version components. [0]: http://manpages.ubuntu.com/manpages/xenial/en/man5/deb-version.5.html [1]: http://manpages.ubuntu.com/manpages/xenial/man8/apt-get.8.html Signed-off-by: Sean Busbey <busbey@apache.org> Signed-off-by: Duo Zhang <zhangduo@apache.org> |
||
---|---|---|
.. | ||
Dockerfile | ||
README.md |
README.md
hbase_docker
Overview
The Dockerfile in this folder can be used to build a Docker image running the latest HBase master branch in standalone mode. It does this by setting up necessary dependencies, checking out the master branch of HBase from GitHub, and then building HBase. By default, this image will start the HMaster and launch the HBase shell when run.
Usage
- Ensure that you have a recent version of Docker installed from docker.io.
- Set this folder as your working directory.
- Type
docker build -t hbase_docker .
to build a Docker image called hbase_docker. This may take 10 minutes or more the first time you run the command since it will create a Maven repository inside the image as well as checkout the master branch of HBase. - When this completes successfully, you can run
docker run -it hbase_docker
to access an HBase shell running inside of a container created from the hbase_docker image. Alternatively, you can typedocker run -it hbase_docker bash
to start a container without a running HMaster. Within this environment, HBase is built in/root/hbase-bin
.