From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24342 invoked by alias); 22 Mar 2019 16:54:15 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 24333 invoked by uid 89); 22 Mar 2019 16:54:14 -0000 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 Received: from sonic302-21.consmr.mail.ne1.yahoo.com (HELO sonic302-21.consmr.mail.ne1.yahoo.com) (66.163.186.147) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 22 Mar 2019 16:54:13 +0000 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== Received: from sonic.gate.mail.ne1.yahoo.com by sonic302.consmr.mail.ne1.yahoo.com with HTTP; Fri, 22 Mar 2019 16:54:11 +0000 Received: from 75-54-112-187.lightspeed.irvnca.sbcglobal.net (EHLO spikycactus.attlocal.net) ([75.54.112.187]) by smtp425.mail.ne1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 173183c1021c2d8a5eb81d3eb77c34ae for ; Fri, 22 Mar 2019 16:54:11 +0000 (UTC) Date: Fri, 22 Mar 2019 16:54:00 -0000 From: "Mike Gran via cygwin" Reply-To: Mike Gran To: cygwin@cygwin.com Subject: Docker, containers, and Cygwin Message-ID: <20190322165405.GA18393@spikycactus.attlocal.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable User-Agent: Mutt/1.11.3 (2019-02-01) X-IsSubscribed: yes X-SW-Source: 2019-03/txt/msg00540.txt.bz2 Hello good people, This isn't a question so much as a random musing... =46rom 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