All my projects use docker-compose.
In my setup I want every nodejs packages that provides an executable, such as mocha or tsc
to be available globally on the command line.
Continue reading →
After clarifying why I use Docker for every project I set up
let me try to clarify also: Why would I use a docker-compose setup over a single Dockerfile setup?
I had been doing the single Dockerfile setup for quite a while.
I was doing a lot of manual work, that made the setup work. But I don't regret it, it taught me a lot!
But that was not sustainable, and it didn't scale.
Continue reading →
I used to install everything on my machine. I used to have ruby, nodejs, python, java, rebol, red
and all the programming languages and environments, their packagers and tools I needed installed
on my machine. It was heaven. Except for the moment when I had to install a new tool, that needed
a newer version, and the old ones might broke and then I had to choose or reinstall every time, switch to
rvm, nvm, pyenv or something else. For a while vagrant was cool.
Continue reading →
I want to get my nextcloud setup to run using docker-compose, and to start with
I need a linux machine with docker running at start up. This is task #1, it looks
like this blog post
has the answers how to do it.
Continue reading →
I just watched the very good, How to run Nginx inside Docker container
video. In 9 minutes you will learn the basics of docker while starting up an nginx server running on docker.
The real take away for me is the updated docker commands, which are finally as explicit as I always had wished
they had been from the beginning. Like docker container run which was docker run.
Continue reading →
I found a couple hints, but this one might be the best one.
https://github.com/puppeteer/puppeteer/blob/master/docs/troubleshooting.md#running-puppeteer-in-docker
I actually changed parts
Continue reading →
I use docker images to provide the environment for development. My nodejs
is installed only inside the docker image. That means I always map my working directory
into the container. This means I don't need to send no build context to the docker deamon.
Continue reading →
TL;DR use any/all of docker system prune, docker container prune, docker image prune, docker volume prune or docker network prune to free the according space.
Continue reading →