|
| 1 | +<!-- |
| 2 | +Licensed to the Apache Software Foundation (ASF) under one or more |
| 3 | +contributor license agreements. See the NOTICE file distributed with |
| 4 | +this work for additional information regarding copyright ownership. |
| 5 | +The ASF licenses this file to You under the Apache License, Version 2.0 |
| 6 | +(the "License"); you may not use this file except in compliance with |
| 7 | +the License. You may obtain a copy of the License at |
| 8 | +
|
| 9 | + http://www.apache.org/licenses/LICENSE-2.0 |
| 10 | +
|
| 11 | +Unless required by applicable law or agreed to in writing, software |
| 12 | +distributed under the License is distributed on an "AS IS" BASIS, |
| 13 | +WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. |
| 14 | +See the License for the specific language governing permissions and |
| 15 | +limitations under the License. |
| 16 | +--> |
| 17 | + |
| 18 | +# accumulo-proxy-docker |
| 19 | +This documentation covers how to stand up [accumulo-proxy](https://github.com/apache/accumulo-proxy/) within a Docker container. |
| 20 | + |
| 21 | +The guide covers: |
| 22 | +* Building the image |
| 23 | +* Configuring the `proxy.properties` file |
| 24 | +* Selecting an appropriate networking choice |
| 25 | +* Starting and stopping the container |
| 26 | +* Basic troubleshooting tips |
| 27 | + |
| 28 | +It is not recommended using this guide for a production instance of accumulo-proxy at this time. |
| 29 | + |
| 30 | +## Build the image |
| 31 | +Firstly you will need the tarball of accumulo-proxy, this is documented in the [README.md](README.md) but for simplicity run: |
| 32 | +```commandline |
| 33 | +mvn clean package -Ptarball |
| 34 | +``` |
| 35 | + |
| 36 | +Once you have the tarball (should be in ./target/ folder) then invoke the Docker build command to create a container image. |
| 37 | +```commandline |
| 38 | +docker build -t accumulo-proxy:latest . |
| 39 | +``` |
| 40 | + |
| 41 | +## Default Configuration and Quickstart |
| 42 | +By default, the container image expects the following to be true: |
| 43 | +1. Your Accumulo instance name is "myinstance" |
| 44 | +2. Your ZooKeeper is available (and reachable from the container) at localhost:2181 |
| 45 | + |
| 46 | +You can start the proxy using: |
| 47 | +```commandline |
| 48 | +docker run --rm -d -p 42424:42424 --network="host" --name accumulo-proxy accumulo-proxy:latest; |
| 49 | +``` |
| 50 | + |
| 51 | +## Custom proxy.properties |
| 52 | +If you wish to create advanced proxy.properties configuration changes, you should look to volume mount these in when you invoke the `docker run` command, an example is: |
| 53 | +```commandline |
| 54 | +docker run --rm -d -p 42424:42424 -v /path/to/proxy.properties:/opt/accumulo-proxy/conf/proxy.properties --network="host" --name accumulo-proxy accumulo-proxy:latest |
| 55 | +``` |
| 56 | + |
| 57 | +## Networking configuration |
| 58 | +Container networking can be a very specialised subject therefore we document two common practices that should cover the majority of use cases for development. |
| 59 | + |
| 60 | +The proxy container must be able to access both Accumulo and ZooKeeper. |
| 61 | + |
| 62 | +The ZooKeeper location can be configured in the `conf/proxy.properties` file, so you can override this to an acceptable value (see "Custom proxy.properties" section) |
| 63 | + |
| 64 | +In order to communicate with Accumulo the container will need to be able to resolve the FQDN that the servers have registered in ZooKeeper. If using [fluo-uno](https://github.com/apache/fluo-uno) this is very likely the hostname of your development environment. We'll call this my.host.com and IP 192.168.0.1 for the rest of this document. |
| 65 | + |
| 66 | +### Host networking |
| 67 | + |
| 68 | +Host networking is the simplest mechanism but generally only works for linux hosts where Docker has been installed on 'bare metal' e.g. through an RPM. |
| 69 | + |
| 70 | +You can test if this will work for you by executing the following steps |
| 71 | + |
| 72 | +Start the accumulo-proxy container and enter it |
| 73 | +```commandline |
| 74 | +docker run -it --rm -p 42424:42424 --network="host" --name accumulo-proxy accumulo-proxy:latest bash; |
| 75 | +``` |
| 76 | + |
| 77 | +Once inside the container, execute the curl command to attempt to connect to the monitor webserver: |
| 78 | +```commandline |
| 79 | +curl my.host.com:9995 |
| 80 | +``` |
| 81 | + |
| 82 | +If the terminal returns an error such as: |
| 83 | +``` |
| 84 | +curl: (7) Failed to connect to my.host.com 9995: Connection refused |
| 85 | +``` |
| 86 | +then your container cannot see the host, and you will need to look at the next section (Non-Host networking). |
| 87 | + |
| 88 | +If you receive the HTML for the monitor web page then host networking will work for you and you can add `--network="host"` to each Docker command going forward. |
| 89 | + |
| 90 | +An example of using host networking: |
| 91 | +```commandline |
| 92 | +docker run --rm -d -p 42424:42424 --network="host" --name accumulo-proxy accumulo-proxy:latest |
| 93 | +``` |
| 94 | + |
| 95 | +Note: You do not need to map your ports (-p) if using host networking, but we include it for clarity. |
| 96 | + |
| 97 | +For more details see the official Docker documentation: [Use host Networking](https://docs.docker.com/network/host) |
| 98 | + |
| 99 | +### Non-Host networking |
| 100 | +If you run outside of a single node linux installation, e.g. Docker for Mac, Docker for Windows or use a VM to isolate your Docker engine then you will likely need to take this path. |
| 101 | + |
| 102 | +Docker allows you to supply additional addresses to be resolved by the container, and these are automatically added by Docker to the /etc/hosts |
| 103 | + |
| 104 | +For each host add a `--add-host FQDN:IP` entry to your Docker run command, you can add multiple entries if need to, see the official docs covering [network settings](https://docs.docker.com/engine/reference/run/#network-settings). |
| 105 | + |
| 106 | +An example of using this approach: |
| 107 | + |
| 108 | +```commandline |
| 109 | +docker run --rm -d -p 42424:42424 --add-host "my.host.com:192.168.0.1" --name accumulo-proxy accumulo-proxy:latest |
| 110 | +``` |
| 111 | + |
| 112 | +## Cleanup |
| 113 | +Once completed you should stop and remove the container. |
| 114 | +```commandline |
| 115 | +docker stop accumulo-proxy; |
| 116 | +docker rm accumulo-proxy; |
| 117 | +``` |
| 118 | + |
| 119 | +## Troubleshooting |
| 120 | +It can often be difficult to know where to start with troubleshooting inside containers, if you need to enter the container without starting the proxy we support this: |
| 121 | +```commandline |
| 122 | +docker run -it --rm -p 42424:42424 --network="host" --name accumulo-proxy accumulo-proxy:latest bash |
| 123 | +``` |
| 124 | + |
| 125 | +The container is very slim so if need be you can add additional tools using `apt`. |
| 126 | + |
| 127 | +If you wish to manually execute the accumulo-proxy in the container you can: |
| 128 | +```commandline |
| 129 | +/opt/accumulo-proxy/bin/accumulo-proxy -p /opt/accumulo-proxy/conf/proxy.properties |
| 130 | +``` |
| 131 | + |
| 132 | +Some resources for additional help: |
| 133 | +* [Main Accumulo Website](https://accumulo.apache.org/) |
| 134 | +* [Contact Us page](https://accumulo.apache.org/contact-us/) |
0 commit comments