containerd/cmd
Kevin Parsons b2420ebcd1 Fix Windows service panic file to not be read-only
Go 1.14 introduced a change to os.OpenFile (and syscall.Open) on Windows
that uses the permissions passed to determine if the file should be
created read-only or not. If the user-write bit (0200) is not set, then
FILE_ATTRIBUTE_READONLY is set on the underlying CreateFile call.

This is a significant change for any Windows code which created new
files and set the permissions to 0 (previously the permissions had no
affect, so some code didn't set them at all).

This change fixes the issue for the Windows service panic file. It will
now properly be created as a non-read-only file on Go 1.14+.

I have looked over the rest of the containerd code and didn't see other
places where this seems like an issue.

Signed-off-by: Kevin Parsons <kevpar@microsoft.com>
2020-11-24 01:37:00 -08:00
..
containerd Fix Windows service panic file to not be read-only 2020-11-24 01:37:00 -08:00
containerd-shim Integrate sys.SetSubreaper, sys.GetSubreaper in sys/reaper package 2020-05-04 08:44:02 +02:00
containerd-shim-runc-v1 Fix linter errors 2019-07-14 20:49:40 -07:00
containerd-shim-runc-v2 Fix linter errors 2019-07-14 20:49:40 -07:00
containerd-stress Fix density spec generation 2019-09-17 16:21:25 -04:00
ctr ctr: fix the incorrect image unmount error hint 2020-11-11 19:57:31 +08:00
gen-manpages man: move ctr.1, containerd-config to section 8, and fix generation 2020-04-03 12:32:52 +02:00
protoc-gen-gogoctrd Update ttrpc for containerd repo 2018-06-28 09:53:40 -04:00