Running @Docker containers on Windows is cool. Until you run into weird CRLF/LF issues. Will this madness ever end? https:/
Powered by Docker, you can install Dokku on any hardware. Use it on inexpensive cloud providers. Once it's set up on a host, you can push Heroku-compatible applications to it via Git. They'll build using Heroku buildpacks and then run in isolated containers. The end result is your own, single-host version of Heroku.
PWD is a Docker playground which allows users to run Docker commands in a matter of seconds. It gives the experience of having a free Alpine Linux Virtual Machine in browser, where you can build and run Docker containers and even create clusters in Docker Swarm Mode.
The 'daddy' of play-with-k8s.com
PWK is a K8s playground which allows users to run K8s clusters in a matter of seconds. It gives the experience of having a free Alpine Linux Virtual Machine in browser. Under the hood Docker-in-Docker (DinD) is used to give the effect of multiple VMs/PCs.
Track your playback from all your Spotify (unofficial) Connect devices to last.fm without having to set it up on every device.
As the public version seems to be at its user limit, I guess I have to run my own instance here. Fortunately, the script is available and I already started to hack together a Docker container to host a running instance of the script. Check the development at https:/
Upgraded my @openvpn setup. Now with fancy @docker containers, an own DNS (also in a container), AES-256-CBC and stuff. Like it.
Now building @docker from source on aarch64. This happens - surprise, surprise - in a Docker container. Neat.
"ERROR: The Docker Engine version is less than the minimum required by Compose." Living on the bleeding edge is hard...