× docker.service - Docker Application Container Engine
Loaded: loaded (/etc/systemd/system/docker.service; enabled; preset: enabled)
Drop-In: /nix/store/gfh802s9scwvs8r7xg5haxhqq2p8ggl0-system-units/docker.service.d
└─overrides.conf
Active: failed (Result: exit-code) since Tue 2023-11-28 07:56:27 +07; 5h 10min ago
TriggeredBy: × docker.socket
Docs: https://docs.docker.com
Process: 3213 ExecStart=/nix/store/p9ji44qs3ka8k2zxpn542q5pfz3vfnzv-docker-24.0.5/bin/dockerd --config-file=/nix/store/2mz7fdnkfi6z8rapwawj1fgla16wax81-daemon.json (code=exited, status=1/FAILURE)
Main PID: 3213 (code=exited, status=1/FAILURE)
IP: 0B in, 0B out
CPU: 187ms
Nov 28 07:56:27 mightyiam-desktop systemd[1]: docker.service: Scheduled restart job, restart counter is at 3.
Nov 28 07:56:27 mightyiam-desktop systemd[1]: docker.service: Start request repeated too quickly.
Nov 28 07:56:27 mightyiam-desktop systemd[1]: docker.service: Failed with result 'exit-code'.
Nov 28 07:56:27 mightyiam-desktop systemd[1]: Failed to start Docker Application Container Engine.
My system configuration, as far as I can tell, has currently no docker enabled. I certainly don’t have virtualization.docker.enable mentioned in my source files… I did have that enabled in the past. So, question is, how do I find out what this service is doing in my system, please?
Which I find somewhat concerning, because I don’t seem to have virtualization.docker.enable… oh, wait. I do. There’s a part of my configuration that is not checked in. It’s system-specific and brief, so that’s why it’s not checked in. And I didn’t consider virtualisation.docker.enable = true; might be set there. And it was.