I'm currently finding time in the gaps (10-minute unit) to lazily write my second book.

In the article, I wrote an explanation of Docker. I am proud to say that the content is quite good, so I would like to introduce it here.

===== from here =====

By the way, my image of Docker containers is

- A unit of apartment (concubine's house) where you can ask multiple mistresses (different versions of applications) of your sisters or brothers only when you feel like it.

- Communication with the inside of the apartment building is thorough, using only the intercom (port number), so there is no need to set environment variables (PATH or LIB) for the host OS (Windows 10).

- (We engineers refer to this as "not having to pollute the home (host OS) environment").

- If you install two or more different versions of the same app on the same OS (e.g. Windows 10), you won't be able to launch the app correctly, and even if you could, you probably wouldn't be able to run it properly because of the messed up configuration environment.

- When you don't come to need the app, you can 'make the whole apartment disappear, including your mistress,' so there's no aftermath.

===== to here =====

I think this is the correct way to describe Docker containers -- however,

Someone might think that "there's something wrong with Ebata's personality".