The following does NOT need to connect the server, which is another way, where the server provides a secret via http, and the letsencrypt server checks it. But the drawback of that is that you need to run the webserver and later reconfigure it, since this is only needed for the initial cert afaik. So I went the other way. Will see how the renewal works, but I think it should work.
Continue reading →
If you are running out of disk space on your docker host, you can free up some space by removing unused docker images, containers, and volumes. I am running docker-compose and always watch the logs, since the service is not high scale yet, so the log files fill up. This means from time to time I need to free some disk space.
Continue reading →
I am installing nodejs inside a docker container and have this line in the Dockerfile:
Continue reading →
I had sync delays of about 15 seconds, when I changed a file on my MacOS fs and that it was seen as changed inside the docker container. This solved it: colima start --mount-type 9p
Continue reading →
The container build process feels a bit not that transparent, I feel. But using:
docker-compose build --progress=plain
it becomes a bit more transparent.
Continue reading →
I learned just yesterday that Docker Inc. is charging for their Docker Desktop client. Only when certain conditions apply, but still. I am not at all against charging for good products, but now I also understand why the docker app and website wanted me to log in lately. Good time to get rid of it and use the less annoying tools,
I found colima as my new docker runtime, simple, easy, not in my way.
Continue reading →
Inside your docker container you have a wrong time? Then it mostly depends on your timezone. Mostly it is solved by passing in the timezone from your host into the container, e.g. in the docker-compose.yml, by setting TZ environment variable directly, like so.
Continue reading →
I had no idea that docker uses the underlying platform as default also for images that it installs. My Dockerfile that just contained FROM ubuntu and I ran some linux binary in there, it threw:
Continue reading →
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 →