From: Pietro Fontana <Pietro.Fontana@synopsys.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Issues with Cygwin inside Docker
Date: Tue, 29 Jun 2021 16:42:35 +0000 [thread overview]
Message-ID: <MWHPR12MB18713DF5BA478CBB05993E1DC4029@MWHPR12MB1871.namprd12.prod.outlook.com> (raw)
Hi,
I am trying to setup Cygwin inside a Windows Docker container, but I step into the issue described here (https://www.mail-archive.com/cygwin@cygwin.com/msg165792.html) and here (https://github.com/microsoft/hcsshim/issues/835).
I am not able to fully understand what is the conclusion from the thread in the mailing list, what is the best approach to avoid this error?
In my Dockerfile I currently download the setup.exe, install it inside the container, compress the folder with 7z in ZIP format, decompress it and finally the image has Cygwin installed without errors. However, I would like to improve this workflow if possible, also because I am not sure if Cygwin works completely fine after this kind of installation process.
Could someone with more expertise shed some light on the topic?
Best Regards,
Pietro F. Fontana
next reply other threads:[~2021-06-29 16:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-29 16:42 Pietro Fontana [this message]
2021-06-30 21:19 ` Andrey Repin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=MWHPR12MB18713DF5BA478CBB05993E1DC4029@MWHPR12MB1871.namprd12.prod.outlook.com \
--to=pietro.fontana@synopsys.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).