Public | Automated Build

Last pushed: 2 years ago
Short Description
This image provides a Wetty terminal with access to the CoreOS command-line tools
Full Description

Dockerized Wetty for CoreOS CLIs

This image provides a Wetty terminal
with access to the following CoreOS command-line tools:

  • docker
  • fleetctl
  • etcdctl

docker

The Docker CLI requires access to the docker.sock in the host OS in order to communicate with the Docker daemon.
To provide access to the docker.sock you need to mount it into the container using the -v flag:

docker run -p 3000:3000 \
  -v /var/run/docker.sock:/var/run/docker.sock \
  centurylink/coreos-cli-wetty

fleetctl

The Fleet CLI communicates with the Etcd API over HTTP. The Etcd endpoint is specified by setting the
FLEETCTL_ENDPOINT environment variable. The default value is http://10.1.42.1:4001 (10.1.42.1 is
typically the IP address of the docker0 interface in CoreOS) but can be overriden with
the -e flag on the docker run command if necessary.

docker run -p 3000:3000 \
  -v /var/run/docker.sock:/var/run/docker.sock \
  -e FLEETCTL_ENDPOINT=http://17.1.0.10:4001 \
  centurylink/coreos-cli-wetty

Wetty

Once the container is running, the Wetty terminal can be accessed by browsing to [http://localhost:3000]
(assuming 3000 was the port mapping you chose when starting the container) with your Chrome browser. Login
with username term and password term.

Docker Pull Command
Owner
centurylink

Comments (1)
stela5
3 years ago

It bears mentioning not to do this on a public cloud due to this privilege escalation vulnerability: https://github.com/subuser-security/subuser/issues/131 (see also https://github.com/docker/docker/issues/1655)