You know it, you use it, now it's time to improve it. PWD!.
Clone or download
Latest commit 1c6e5a7 Jul 14, 2018
Permalink
Failed to load latest commit information.
config Remove unused config parameters Dec 18, 2017
docker Fix print formatting errors Feb 24, 2018
dockerfiles Fix broken URL to nginx-app.yaml (#260) May 9, 2018
event When playground is created or modified it emits an event. (#225) Nov 23, 2017
handlers Fix typo Apr 30, 2018
haproxy Add k8s styles Nov 29, 2017
id Refactor id generator to it's own package Sep 14, 2017
k8s Make KubeletClient public Nov 21, 2017
provisioner Add support for file editor Jan 5, 2018
pwd Remove unused code Feb 27, 2018
router Make router director return extra information (needed to route ssh Oct 31, 2017
scheduler Fix print formatting errors Feb 24, 2018
storage Allow to decide which tasks are going to be executed per playground (#… Nov 21, 2017
www Add sessionId to instance upon received event Jul 15, 2018
.gitignore Vendor dependencies and use docker/go-docker for API types Oct 20, 2017
Dockerfile Make ping not use docker/docker and update Dockerfiles Nov 9, 2017
Dockerfile.l2 Make ping not use docker/docker and update Dockerfiles Nov 9, 2017
Gopkg.lock Update crypto May 28, 2018
Gopkg.toml Update Gorilla handlers and add CORS option Feb 19, 2018
LICENSE Change import statements accordingly May 8, 2017
README.md Https I'll TLD doesn't work Dec 5, 2017
api.go Allow to decide which tasks are going to be executed per playground (#… Nov 21, 2017
docker-compose.yml Remove hybrid image from compose as it's not needed anymore. Nov 24, 2017
prometheus.yml More prometheus metrics Jun 14, 2017

README.md

play-with-docker

Play With Docker gives you the experience of having a free Alpine Linux Virtual Machine in the cloud where you can build and run Docker containers and even create clusters with Docker features like Swarm Mode.

Under the hood DIND or Docker-in-Docker is used to give the effect of multiple VMs/PCs.

A live version is available at: http://play-with-docker.com/

Requirements

Docker 1.13+ is required.

The docker daemon needs to run in swarm mode because PWD uses overlay attachable networks. For that just run docker swarm init in the destination daemon.

It's also necessary to manually load the IPVS kernel module because as swarms are created in dind, the daemon won't load it automatically. Run the following command for that purpose: sudo modprobe xt_ipvs

Development

Start the Docker daemon on your machine and run docker pull franela/dind.

  1. Install go 1.7.1+ with brew on Mac or through a package manager.

  2. Install dep and run dep ensure to pull dependencies

  3. Start PWD as a container with docker-compose up.

  4. Point to http://localhost and click "New Instance"

Notes:

  • There is a hard-coded limit to 5 Docker playgrounds per session. After 4 hours sessions are deleted.
  • If you want to override the DIND version or image then set the environmental variable i.e. DIND_IMAGE=franela/docker<version>-rc:dind. Take into account that you can't use standard dind images, only franela ones work.

Port forwarding

In order for port forwarding to work correctly in development you need to make *.localhost to resolve to 127.0.0.1. That way when you try to access to pwd10-0-0-1-8080.host1.localhost, then you're forwarded correctly to your local PWD server.

You can achieve this by setting up a dnsmasq server (you can run it in a docker container also) and adding the following configuration:

address=/localhost/127.0.0.1

Don't forget to change your computer default DNS to use the dnsmasq server to resolve.

Building the dind image myself.

If you want to make changes to the dind image being used, make your changes to the Dockerfile.dind file and then build it using this command: docker build --build-arg docker_storage_driver=vfs -f Dockerfile.dind -t franela/dind .

FAQ

How can I connect to a published port from the outside world?

If you need to access your services from outside, use the following URL pattern http://ip<hyphen-ip>-<session_jd>-<port>.direct.labs.play-with-docker.com (i.e: http://ip-2-135-3-b8ir6vbg5vr00095iil0-8080.direct.labs.play-with-docker.com).

Why is PWD running in ports 80 and 443?, Can I change that?.

No, it needs to run on those ports for DNS resolve to work. Ideas or suggestions about how to improve this are welcome