github/containerd
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases 2 Wiki Activity

Set explicit ACL on test files

Browse Source 
It seems that the default ACLs inherited from the parent folder
on Windows Server 2022, does not include "CREATOR OWNER" as it
does on Windows Server 2019. This sets explicit ACLs on test
files.

Signed-off-by: Gabriel Adrian Samfira <gsamfira@cloudbasesolutions.com>
This commit is contained in:
Gabriel Adrian Samfira 2021-12-03 13:30:08 +02:00
parent 106086d65a
commit 9cc0d1f073
No known key found for this signature in database
GPG Key ID: 7D073DCC2C074CB5
2 changed files with 11 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
integration/images/volume-copy-up/Dockerfile_windows
View File

@ -26,8 +26,11 @@ RUN cmd.exe /c "@echo off && FOR %i in (%BUSYBOX_EXES%) do (mklink %i.exe busybo
USER ContainerUser
RUN cmd.exe /c mkdir C:\test_dir
RUN mkdir C:\test_dir
# Explicitly set full access rights for "CREATOR OWNER". While
# this is set by default for Windows Server 2019, it seems that
# on Windows Server 2022 it is not.
RUN icacls C:\test_dir /grant "CREATOR OWNER":(OI)(CI)(IO)F /T
RUN /bin/sh.exe -c "echo test_content > /test_dir/test_file"
ENV PATH="C:\bin;C:\Windows\System32;C:\Windows;"

8
integration/images/volume-ownership/Dockerfile_windows
View File

@ -25,10 +25,14 @@ WORKDIR C:/bin
ADD tools/get_owner_windows.exe C:/bin/get_owner.exe
RUN cmd.exe /c "@echo off && FOR %i in (%BUSYBOX_EXES%) do (mklink %i.exe busybox.exe)"
RUN cmd.exe /c mkdir C:\volumes
USER ContainerUser
RUN mkdir C:\volumes
# Explicitly set full access rights for "CREATOR OWNER". While
# this is set by default for Windows Server 2019, it seems that
# on Windows Server 2022 it is not.
RUN icacls C:\volumes /grant "CREATOR OWNER":(OI)(CI)(IO)F /T
RUN mkdir C:\volumes\test_dir
RUN /bin/sh.exe -c "echo test_content > /volumes/test_dir/test_file"