{"push_id":1331739138,"size":1,"distinct_size":1,"ref":"refs/heads/servicing_fix","head":"5fe73ec931f3fc25020796c33e35b9dc3c1e8b16","before":"147e2977355d4c530e1f9302a7a0c3281690881b","commits":[{"sha":"5fe73ec931f3fc25020796c33e35b9dc3c1e8b16","author":{"name":"Stefan J. Wernli","email":"c69c29465d2bce7cb91f90af1abe7fe9be8af46b@microsoft.com"},"message":"Fixing servicing bug by always specifying LayerFolderPath\n\nDuring the recent OCI changes, I mistakenly thought LayerFolderPath is only needed for Windows Server containers (isolation=process) and not for Hyper-V Containers, but it turns out it is also required for servicing containers used to finish installing updates.  Since the servicing containers need to reuse the container's create options, this change makes it so that LayerFolderPath is always filled in for all containers as part of constructing the create options.\n\nSigned-off-by: Stefan J. Wernli <swernli@microsoft.com>","distinct":true,"url":"https://api.github.com/repos/swernli/docker/commits/5fe73ec931f3fc25020796c33e35b9dc3c1e8b16"}]}
{"actor":{"display_login":"swernli"}}