X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:reply-to:to:subject:message-id
	:mime-version:content-type:content-transfer-encoding; q=dns; s=
	default; b=cv6379cqVdwcnUzIGXQ4NZrdzfgKkeNfbaNUQQ5LsulzIrEINdf3r
	+OxHGa3N6G3rHo/Bwx1yWt99wXwExH6qvVHBp8wmgZCw56tH4rnYrN/VROl2oeLm
	m+fFezw9Gu0wroPqbdVjl+7udM0v48dQM1YWYjG8fa8f7BtPnrkj14=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:reply-to:to:subject:message-id
	:mime-version:content-type:content-transfer-encoding; s=default;
	bh=0qB0Uxj63yu8P1lfvgZa6z9Owb0=; b=d0j0MU7yHY8zZfph492Snl6jp22s
	zK5N4tGAkyNQXa/DpNbFDQcJDCKU4dpjsDMvTGvHzXp2sIcu2EKVRyvWlcMD2Dsg
	pn2A+RL8HPY3jEtvEpQSvIcd9xoTmhZ85QMRturSsSmdlftR6bqDuzWNk6qyK5Go
	jhc6Afs8K83T4ZM=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Authentication-Results:	sourceware.org; auth=none
X-Spam-SWARE-Status:	No, score=-1.6 required=5.0 tests=BAYES_00,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=no version=3.3.1 spammy=gran, intercepted, H*F:D*yahoo.com, today's
X-HELO:	sonic302-21.consmr.mail.ne1.yahoo.com
DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1553273651; bh=KSsvJqVrD5K9zRSTErTqYernSU8zuBUWv1L/3KC2vi0=; h=Date:From:To:Subject:From:Subject; b=ZYPP/Z2Yvc5wE9AeKTyV4/NPZG9AuY3lvrwvlUjoL1XujE4TwB8teO1bQYxHiypW7DPiQ2+F1KytwKxSYp6Bjl2E7anMVZNl6t9/M/yxuqJwNybHa7TBn/hE/eQ0p74Ux5qy5DUy8D6WGIQ+ypGaXhKh0TJrs5zMGigyIFVdE0yPr1u5RoJ35Tjk3bokIvvwmkorGTBw4cbOShHDSOzV8Z+BENx19ccW8dwtA54V2R5K+0y7dENwT/bdM3ddt5eZlnNt8EyJEKRZG8Ph5c7aZHbyOKMmvHCcmYD3vKEJr4sLhjngYs7c7ymBOQ0hnSQC1VClhH5ZbM0XhHhar855gQ==
Date:	Fri, 22 Mar 2019 09:54:05 -0700
From:	"Mike Gran via cygwin" <cygwin AT cygwin DOT com>
Reply-To:	Mike Gran <spk121 AT yahoo DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Docker, containers, and Cygwin
Message-ID:	<20190322165405.GA18393@spikycactus.attlocal.net>
MIME-Version:	1.0
User-Agent:	Mutt/1.11.3 (2019-02-01)
X-IsSubscribed:	yes
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id x2MGsQSF027541

Hello good people,

This isn't a question so much as a random musing...

From what I understand, Cygwin works by translating POSIX-like calls
into Windows API.  Or, to be more specific, the version of newlib that
Cygwin provides links to Windows-provided dlls that make Windows API
calls.

And Docker on Windows works by creating a layer that allows some
subset of the Windows API to be called by the image in the container,
passing those API calls to the OS kernel.

I tried (non-exhaustively) to figure out what Windows kernel APIs can
actually make it through the Docker infrastructure from an image to
the Windows kernel. This led me to ponder if the Windows APIs that
Cygwin uses in its emulation layer are a subset of the APIs that make
it through the Windows Docker containers.

My guess is that all the API that Cygwin uses *would* pass through
container, since is it basic stuff.  (Of course, the file and socket
I/O may be intercepted by the container depending on its permissions.)

Unfortunately, there doesn't seem to be handy reference about how
Windows Docker containers work.

Anyway, that's today's musing.

-Mike Gran

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

- Raw text -