https://webwork.blog/en/tags/docker/Recent content in Docker on WebWork BlogHugoen-USTue, 28 Mar 2023 10:00:00 +0000https://webwork.blog/en/cli-command-w-on-linux-unix/Tue, 28 Mar 2023 10:00:00 +0000https://webwork.blog/en/cli-command-w-on-linux-unix/Even with years of experience in IT you keep running into something new. Recently I came across the CLI command w. w gives a quick overview of which users are currently logged in to the system and what they are doing.https://webwork.blog/en/change-docker-subnets/Tue, 04 May 2021 20:34:25 +0000https://webwork.blog/en/change-docker-subnets/Docker is wasteful with IP subnets by default. On hosts with many networks, this sooner or later leads to the following error: Error response from daemon: could not find an available, non-overlapping IPv4 address pool among the defaults to assign to the network Looking at the created networks, the following pattern becomes apparent:https://webwork.blog/en/timezones-in-docker-containers/Tue, 23 Mar 2021 20:00:00 +0000https://webwork.blog/en/timezones-in-docker-containers/While reviewing logs from various Docker containers I ran into an issue: some containers were running with the host's local timezone (CET), others with UTC. While debugging I even spotted a third timezone in another container. The reason: every developer can pin an arbitrary timezone in their Dockerfile in 1–2 lines — definitely not a best practice, but it happened in one of the containers I was using.