A simple Minecraft Docker client, to visualize and manage Docker containers.
WARNING: Please use Dockercraft on your local machine only. It currently doesn't support authentication. Every player should be considered a root user!
-
Install Minecraft: minecraft.net
The Minecraft client hasn't been modified, just get the official release.
-
Pull or build Dockercraft image: (an offical image will be available soon)
docker pull gaetan/dockercraft
or
git clone git@github.com:docker/dockercraft.git docker build -t gaetan/dockercraft dockercraft
-
Run Dockercraft container:
docker run -t -i -d -p 25565:25565 \ -v /var/run/docker.sock:/var/run/docker.sock \ --name dockercraft \ gaetan/dockercraft
Mounting
/var/run/docker.sock
inside the container is necessary to send requests to the Docker remote API.The default port for a Minecraft server is 25565, if you prefer a different one:
-p <port>:25565
-
Open Minecraft > Multiplayer > Add Server
The server address is the IP of Docker host. No need to specify a port if you used the default one.
If you're using Docker Machine:
docker-machine ip <machine_name>
-
Join Server!
You should see at least one container in your world, which is the one hosting your Dockercraft server.
You can start, stop and remove containers interacting with levers and buttons. Some Docker commands are also supported directly via Minecraft's chat window, which is displayed by pressing the
T
key (default) or/
key.
A command always starts with a
/
.If you open the prompt using the
/
key, it will be prefilled with a/
character, but if you open it with theT
key, it will not be prefilled and you will have to type a/
yourself before typing your docker command.example:
/docker run redis
.
This is just the beginning for Dockercraft! We should be able to support a lot more Docker features like:
- List Docker Machines and use portals to see what's inside
- Support more Docker commands
- Display logs (for each container, pushing a simple button)
- Represent links
- Docker networking
- Docker volumes
- ...
If you're interested about Dockercraft's design, discussions happen in that issue. Also, we're using Magicavoxel to do these nice prototypes:
You can find our Magicavoxel patterns in that folder.
To get fresh news, follow our Twitter account: @dockercraft.
The Minecraft client itself remains unmodified. All operations are done server side.
The Minecraft server we use is http://cuberite.org. A custom Minecraft compatible game server written in C++. github repo
This server accepts plugins, scripts written in Lua. So we did one for Docker. (world/Plugins/Docker)
Unfortunately, there's no nice API to communicate with these plugins. But there's a webadmin, and plugins can be responsible for "webtabs".
Plugin:AddWebTab("Docker",HandleRequest_Docker)
Basically it means the plugin can catch POST requests sent to http://127.0.0.1:8080/webadmin/Docker/Docker
.
Events from the Docker remote API are transmitted to the Lua plugin by a small daemon (written in Go). (go/src/goproxy)
func MCServerRequest(data url.Values, client *http.Client) {
req, _ := http.NewRequest("POST", "http://127.0.0.1:8080/webadmin/Docker/Docker", strings.NewReader(data.Encode()))
req.Header.Set("Content-Type", "application/x-www-form-urlencoded")
req.SetBasicAuth("admin", "admin")
client.Do(req)
}
The goproxy binary can also be executed with parameters from the Lua plugin, to send requests to the daemon:
function PlayerJoined(Player)
-- refresh containers
r = os.execute("goproxy containers")
end
Want to hack on Dockercraft? Docker's contributions guidelines apply.