X-Recipient: archive-cygwin AT delorie DOT com
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org D8FE9386F40C
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1598468793;
	bh=SD0HtWwcygtpDF27pF/tzNAZWHqi2ABZM5jZvpxml2w=;
	h=References:In-Reply-To:Date:Subject:To:List-Id:List-Unsubscribe:
	 List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc:
	 From;
	b=TrfzpQkHRQa5/EMtEYn/dG1FfRD+Ve9QO88upjzA2Zz33RfApy+F3YR7hZMMQ60pY
	 /KpGhMBk3UoTusgMq355+8AzmjtinXqH/58zRNzOmgoAtC6bMF79CKTnLWRd1WzS0s
	 /olj+C3eC8pN/xc5rbme+A0aST678KTXYi5tpKkk=
X-Original-To: cygwin AT cygwin DOT com
Delivered-To: cygwin AT cygwin DOT com
DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org A5A92384C004
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20161025;
 h=x-gm-message-state:mime-version:references:in-reply-to:from:date
 :message-id:subject:to:cc;
 bh=id6eZv/c099zd5cVL8rMnikTErUSTV1GKT2WttwZPT0=;
 b=LuW6rAFvipmno3GOWZgUqJT2WnSKrSkC2+MkqPewvpjWlzl6WATXL/qC7Auwa0OPBA
 3sfmtKtIJTocdbT2iSUqloca942NKWFZkiH+tmKvCoNeaTywQJ3a1O0qFE1ZRnRMGEyU
 lvBbSDftsHSvI0zcD+kdS2pPHIt66SS/UdruBG2nE3dcCJuuP4IoRPRSlSD2L8NzXs0e
 8gtESwFfQWQK8NZWV8ecIjVOhgttjSi04/emIUhuYc9aYuOBuGPiGpj0UGCAx1mIf4QX
 /Z7QTpxKTs/zvwSbHTr3MEw+svaHLT/PRnfI/J6EWAK+m0iONAtMXPbJkBaDYUm35BW4
 ht8Q==
X-Gm-Message-State: AOAM532yZ5mGiO4kIDCqos9wpo+kW8QfuXoKpi1NPaaCuSyv8v0dnvQ3
 xModsHc1Qjv4u1VLdtPX49iztet9FL18WD7+UgZooglpysXyQ72O7nM=
X-Google-Smtp-Source: ABdhPJzMKysrF10VxEq53t1+88GUuK1IcmB6Gr7hx2CAP8tlPvkVs3lj6FoAHfcZ6YrxmTPAs3SzStRenJxk2iIzOJs=
X-Received: by 2002:a67:e3cc:: with SMTP id k12mr3231446vsm.173.1598468790156; 
 Wed, 26 Aug 2020 12:06:30 -0700 (PDT)
MIME-Version: 1.0
References: <CAALQ5rnxo0_pJqTo5+617sZ6NPyDEuw5LkK_w5tMihYnTRfHrg AT mail DOT gmail DOT com>
 <875z95tg5c DOT fsf AT Rainer DOT invalid>
In-Reply-To: <875z95tg5c.fsf@Rainer.invalid>
Date: Wed, 26 Aug 2020 21:06:12 +0200
Message-ID: <CAALQ5rmWfeDm1H8dSgKcRbxJazDYeYFKyt-niCPp4KhbTJ9G4A@mail.gmail.com>
Subject: Re: Forcing setup.exe not to create WSL symlinks
To: Achim Gratz <Stromeko AT nexgo DOT de>
X-Spam-Status: No, score=-2.4 required=5.0 tests=BAYES_00, DKIM_SIGNED,
 DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, HTML_MESSAGE,
 KAM_EXEURI, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS,
 TXREP autolearn=no autolearn_force=no version=3.4.2
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on
 server2.sourceware.org
X-Content-Filtered-By: Mailman/MimeDel 2.1.29
X-BeenThere: cygwin AT cygwin DOT com
X-Mailman-Version: 2.1.29
List-Id: General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Archive: <https://cygwin.com/pipermail/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe: <https://cygwin.com/mailman/listinfo/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
From: Michael Wild via Cygwin <cygwin AT cygwin DOT com>
Reply-To: Michael Wild <themiwi AT gmail DOT com>
Cc: The Cygwin Mailing List <cygwin AT cygwin DOT com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: "Cygwin" <cygwin-bounces AT cygwin DOT com>

On Wed, Aug 26, 2020 at 8:31 PM Achim Gratz wrote:

> Michael Wild via Cygwin writes:
> > Is there a way to disable WSL symlinks when installing Cygwin with
> > setup.exe? Problem is that Docker on Windows apparently doesn't support
> > them (see https://github.com/moby/moby/issues/41058). I would like to
> use a
> > custom Docker image for GitHub Actions to reproducibly build my packages
> > but am failing to build the base image because of this.
>
> That description is not very clear.  If the symlinks are created during
> postinstall, then they should obey the value of CYGWIN environment that
> is in effect at that time.  If so, then the behaviour should start
> appearing with cygwin-3.1.5, which is the first release that has the
> code supporting these (and makes them the default).  I'm not aware that
> the behaviour of setup.exe has changed in that respect recently, but I
> haven't checked thoroughly.
>
>
> Regards,
> Achim.
>
>
In order to reproduce, run the following commands on Windows:

> docker run --name setup -it
mcr.microsoft.com/windows/servercore:10.0.17763.1397-amd64

Once inside the container, run:

> powershell
PS> $env:CYGWIN=winsymlinks:lnk
PS> mkdir \tmp
PS> cd \tmp
PS> Invoke-WebRequest -Uri https://www.cygwin.com/setup-x86_64.exe -OutFile
setup-x86_64.exe
PS> .\setup-x86_64.exe -W -n -q -R C:\Cygwin64 -s
http://mirrors.kernel.org/sourceware/cygwin/ -P default
PS> Wait-Process -Name setup-x86_64
PS> fsutil reparsePoint query C:\cygwin64\dev\fd

The last command will output something like:

Reparse Tag Value : 0xa000001d
Tag value: Microsoft
Tag value: Name Surrogate

Reparse Data Length: 0x00000011
Reparse Data:
0000: 02 00 00 00 2f 70 72 6f 63 2f 73 65 6c 66 2f 66 ..../proc/self/f
0010: 64

So, the CYGWIN variable got ignored.

If you want, you can try to run a Cygwin shell:

PS> C:\Cygwin64\bin\bash.exe --login -i

For me this works fine. Then, exit the container and try to commit it:

PS> exit
> exit
> docker commit setup cygwin:latest

The last command then errors out with:

Error response from daemon: re-exec error: exit status 1: output:
time="2020-08-26T21:00:55+02:00" level=error msg="hcsshim::ImportLayer -
failed failed in Win32: The system cannot find th
e path specified. (0x3)" error="hcsshim::ImportLayer - failed failed in
Win32: The system cannot find the path specified. (0x3)"
importFolderPath="C:\\ProgramData\\Docker\\tmp\\hcs00092524
3"
path="\\\\?\\C:\\ProgramData\\Docker\\windowsfilter\\c31ac616438460478e6cc6e5526ee664e620ba4479da433bcabb6d2a76880ef4"
hcsshim::ImportLayer - failed failed in Win32: The system cannot find the
path specified. (0x3)

Does this help diagnosing the problem?

Kind regards

Michael
--
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple