{"push_id":914473013,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"79b4e5a8d7efe534647e2d5287f606883fc555a3","before":"0fda4ff7152dd9c59441a6ab1f4c48978f2a4a30","commits":[{"sha":"79b4e5a8d7efe534647e2d5287f606883fc555a3","author":{"email":"52a70820ecd7a0ea34dd5639534e93546b5e0b21@gmail.com","name":"Benno Fünfstück"},"message":"docker module: fix kernel module loading\n\nThe docker module used different code for socket-activated docker daemon than for the non-socket activated daemon.\nIn particular, if the socket-activated daemon is used, then modprobe wasn't set up to be usable and in PATH for\nthe docker daemon, which resulted in a failure to start the daemon with overlayfs as storageDriver if the\n`overlay` kernel module wasn't already loaded. This commit fixes that bug (which only appears if socket\nactivation is used), and also reduces the duplication between code paths so that it's easier to keep\nboth in sync in future.","distinct":true,"url":"https://api.github.com/repos/NixOS/nixpkgs/commits/79b4e5a8d7efe534647e2d5287f606883fc555a3"}]}