proxy Docker container service for Gearbox
This is the repository for the proxy Docker container implemented for Gearbox.
GitHub commit:
GitHub release(latest): 
| Service | GitHub Version | Docker Version | Docker Size | Docker Tags |
|---|---|---|---|---|
| proxy |  |
 |
 |
(1.10.3, 1.10) |
| proxy |  |
 |
 |
(1.11.13, 1.11) |
| proxy |  |
 |
 |
(1.12.2, 1.12) |
| proxy |  |
 |
 |
(1.13.12, 1.13) |
| proxy |  |
 |
 |
(1.14.2, 1.14) |
| proxy |  |
 |
 |
(1.15.12, 1.15) |
| proxy |  |
 |
 |
(1.16.1, 1.16) |
| proxy |  |
 |
 |
(1.17.10, 1.17) |
| proxy |  |
 |
 |
(1.18.0, 1.18, latest) |
A driving force behind Gearbox is to improve the user experience using software, and especially for software developers.
Our vision is to empower developers and other software users to quickly and easily use almost any version of a software service, command line tool or API without without first getting bogged down with installation and configuration.
In other words, our vision for Gearbox users is that software "just works".
This container has been designed to work within the Gearbox framework. However, due to the flexability of Gearbox, it can be used outside of this framework.
There are three methods:
launch is a tool specifically designed to interact with a Gearbox Docker container.
It provides three important functional areas, without any Docker container learning curve:
- Allows control over Gearbox Docker containers: stop, start, create, remove.
- Build, update, modify and release Docker images.
- Acts as a proxy for interactive commands within a Gearbox Docker container.
It also provides a functional SSH daemon for connecting remotely as well as a standard set of common tools and utilities.
Further launch documentation can be found here.
launch is currently in beta testing and is included along with all Gearbox Docker repos.
Once out of beta, it will be included within the Gearbox installation package.
For now, simply download the standalone launch binary for your O/S.
There are many ways to call launch, either directly or indirectly. Additionally, all host environment variables will be imported into the container seamlessly. This allows a devloper to try multiple versions of software as though they were installed locally.
If a container is missing, it will be downloaded and created. Multiple versions can co-exist.
Install, create, and start the proxy Gearbox container.
./launch install proxy
Create, and start the proxy Gearbox container. Run a shell.
./launch shell proxy
Create, and start the proxy Gearbox container with version 1.11.13 and run a shell.
./launch shell proxy:1.11.13
./launch shell proxy:1.11.13 ls -l
./launch shell proxy:1.11.13 ps -eaf
If proxy is symlinked to launch, then the Gearbox container will be determined automatically and the default command will be run.
All available commands for a Gearbox container will be automatically symlinked upon installation.
./proxy
Running proxy Gearbox container default command. If a container has a default interactive command, arguments can be supplied without specifying that command.
./proxy -flag1 -flag2 variable
./launch proxy:1.11.13 -flag1 -flag2 variable
Gearbox containers may have multiple executables that can be run. The proxy Gearbox container has the following available commands:
- The default command will execute `` within the container.
ssh - All Gearbox containers have a running SSH daemon. So you can connect remotely. To show what ports are exported to the host, use the following command.
./launch list proxy
Simply clone this repository to your local machine
git clone https://github.com/gearboxworks/docker-proxy.git
make build - Build Docker images. Build all versions from the base directory or specific versions from each directory.
make list - List already built Docker images. List all versions from the base directory or specific versions from each directory.
make clean - Remove already built Docker images. Remove all versions from the base directory or specific versions from each directory.
make push - Push already built Docker images to Docker Hub, (only for Gearbox admins). Push all versions from the base directory or specific versions from each directory.
You can either build your container as above, or use it from DockerHub with these commands:
make start - Spin up a Docker container with the correct runtime configs.
make stop - Stop a Docker container.
make run - Run a Docker container in the foreground, (all STDOUT and STDERR will go to console). The Container be removed on termination.
make shell - Run a shell, (/bin/bash), within a Docker container.
make rm - Remove the Docker container.
make test - Will issue a stop, rm, clean, build, create and start on a Docker container.
A simple docker pull gearbox/proxy will pull down the latest version.
start - Spin up a Docker container with the correct runtime configs.
docker run -d --name proxy-latest --restart unless-stopped --network gearboxnet gearbox/proxy:latest
stop - Stop a Docker container.
docker stop proxy-latest
rm - Remove the Docker container.
docker container rm proxy-latest
run - Run a Docker container in the foreground, (all STDOUT and STDERR will go to console). The Container be removed on termination.
docker run --rm --name proxy-latest --network gearboxnet gearbox/proxy:latest
shell - Run a shell, (/bin/bash), within a Docker container.
docker run --rm --name proxy-latest -i -t --network gearboxnet gearbox/proxy:latest /bin/bash
ssh - All Gearbox containers have a running SSH daemon. So you can connect remotely.
Either use launch above or discover the port and SSH directly.
SSH_PORT="$(docker port proxy-latest 22/tcp | sed 's/0.0.0.0://')"
ssh -p ${SSH_PORT} -o StrictHostKeyChecking=no gearbox@localhost