yarmo/yarmo.eu
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Fix typos
All checks were successful
continuous-integration/drone/push Build is passing
Details

Browse Source
This commit is contained in:
Yarmo Mackenbach 2020-06-14 09:31:44 +02:00
parent 6837aaeafe
commit 5368d2fff3
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
content/blog/2020-06-05--missing-entropy.md
View File

@ -18,7 +18,7 @@ Sticking with what I'm comfortable with, I decided to go with a docker setup wit
- [php-fpm](https://hub.docker.com/_/php) as PHP processor
- a couple of others with minor significance
As per usual, I write my `docker-compose.yaml` and it's all set. Except this time. Sometimes, when I would change something in the yaml file and run `docker-compose up -d`, it would do it immediately, as I would expect from all the times I've run it on my homelab. But sometimes, it would wait a minute or longer and only execute then.
As per usual, I write my `docker-compose.yaml` and it's all set. But not this time. At times, when I would change something in the yaml file and run `docker-compose up -d`, it would do it immediately, as I would expect from all the times I've run it on my homelab. But sometimes, it would wait a minute or longer and only execute then.
I accepted this behavior a few times, but at some point, it had to be dealt with.
@ -60,7 +60,7 @@ Apparently, Docker is an application that requires randomness. But how have I ne
On both my desktop computer and homelab, the entropy available is around `4000`, which is perfect. They are able to maintain this entropy because of all the sources of randomness available to them. Mouse and keyboard inputs, processes running in the background, etc.
Now, let's the VPS as a counter example. These things are made to be fully reproducible: every time you boot one up, they are expected to run in the same way. They are also very sealed off from the host system for security reasons: I cannot read core temperature values for my VPS. They don't have "true hardware", they get portions of hardware, shared with other VPS instances. Except for my SSH connection, the VPS has no mouse or keyboard inputs.
Now, let's take the VPS as a counter example. These things are made to be fully reproducible: every time you boot one up, they are expected to run in the same way. They are also very sealed off from the host system for security reasons: I cannot read core temperature values for my VPS. They don't have "true hardware", they get portions of hardware, shared with other VPS instances. Except for my SSH connection, the VPS has no mouse or keyboard inputs.
In other words, VPSs are severely lacking in sources of entropy. That is why the entropy available was only `52` and why docker stalled: it had to wait for sufficient randomness to occur.