Epic: Windows support - Githubissues

bfirsh commented 9 years ago

This is a meta-issue for keeping track of all the things we're doing around Windows support for Compose.

Various things that are part of this:

Building a binary on Windows. PyInstaller, the method we currently use to build binaries for Linux and OS X, also works with Windows. In theory this should just work. It would be useful to have build scripts etc to automate this.
Run Compose inside a container. This may be be easier than building a native binary for Windows. https://github.com/docker/compose/issues/169 https://github.com/docker/compose/pull/1806
Making Compose Windows compatible. I expect this will be mostly making sure paths work and getting the TTYs to work.
Volume sharing. When running Compose on OS X, it expects /Users to be mounted in the right place so volumes work. I wonder if we need something added to Machine/boot2docker to make volumes work as expected on Windows. (The Compose quick start guide has a demonstration of how volumes are used to mount code inside a container.)
Run CI tests on Windows. We don't all test on Windows, so we'd have to be careful about regressions. https://github.com/docker/compose/issues/886

Steps:

[x] Investigate whether binaries will build cleanly on Windows https://github.com/docker/compose/issues/1051
[x] Investigate whether running Compose inside a container will be easier than running it natively on Windows

Related issues:

https://github.com/docker/compose/issues/598

T1m1 commented 9 years ago

Same here! :+1:

atrauzzi commented 9 years ago

Awesome!

Any idea when this will make it into the standard Windows release of Docker Toolbox?

skygeo commented 9 years ago

Awesome! Works like a charm in windows 7 !

christianhuening commented 9 years ago

@atrauzzi: i would like to know the same

divyakumarjain commented 9 years ago

Works for me with Phython27, pip on Windows 8.1.

jamespacileo commented 9 years ago

Weird issues on Windows 10, but I think it's Vagrant and toolbox :)

Very excited to try this out! Thank you!! :smile:

Duske commented 9 years ago

Works for me with Python3.4, pip, docker toolbox 1.8.2c and Windows 8.1. Awesome that I can start using docker-compose.yml :)

atrauzzi commented 9 years ago

What's the preferred way to get Python installed nowadays? I'd rather wait for toolbox to update, but if that isn't soon enough, I suppose I can get it set up.

parhamdoustdar commented 9 years ago

I personally get a "Touple out of range" whenever I run the command to install docker-compose with pip.

On 10/2/2015 11:44 PM, Alexander Trauzzi wrote:

What's the preferred way to get Python installed nowadays? I'd rather wait for toolbox to update, but if that isn't soon enough, I suppose I can get it set up.

— Reply to this email directly or view it on GitHub https://github.com/docker/compose/issues/1085#issuecomment-145143680.

au-phiware commented 9 years ago

I happily run docker-compose inside a container with these scripts: Powershell scripts for Docker Toolbox for Windows

dnephin commented 9 years ago

I think we can close this issue now.

Master includes support for building a windows binary and support for running compose from an image. Any remaining bugs have their only issues for tracking.

If you run into any problems, please do open an issue about it. Current open issues should be tagged with group/windows: https://github.com/docker/compose/issues?q=is%3Aopen+is%3Aissue+label%3Agroup%2Fwindows

dnephin commented 9 years ago

@au-phiware would you be interested in opening a PR with those scripts? We currently have https://github.com/docker/compose/blob/master/script/run.sh for running the image on linux/osx.

It would be great to include a version that works on windows. It can use the official image we publish (or will be publishing) at docker/compose:<tag>

atrauzzi commented 9 years ago

Just mentioning this here in case people are trying to use bind mounts: #2158

Hopefully it saves you some googling/bug reporting!

kobenauf commented 8 years ago

This was closed over 6 months ago, but volumes still don't mount on Windows (unless they are under c:/users), there is not an easy way to develop on files locally that are then picked up and run by the docker service (unless I am able/willing to move my code to c:/users), and interactive mode is still not supported. Does anyone know if there are specific tickets for those issues I can watch?

friism commented 8 years ago

@kobenauf with beta Docker for Mac and Windows we're trying to address some of these shortcomings: https://blog.docker.com/2016/03/docker-for-mac-windows-beta/

kobenauf commented 8 years ago

Thanks @friism, I'm super happy to hear that! I've submitted my information a couple times for that beta program but never heard back from anybody. Do you happen to know when it might be expanded to more people, and is there any anticipated release date yet?

airtonix commented 7 years ago

docker compose does not properly handle windows environment variables.

example (it's powershell, but I'm using pshazz which changes the prompt to look more unixy):

~ $ echo $SSH_AUTH_SOCK
# blank

~ $ echo $Env:SSH_AUTH_SOCK
/tmp/ssh-qgFBji4276/agent.4276

~ $ gci Env:\SSH_AUTH_SOCK

Name                           Value
----                           -----
SSH_AUTH_SOCK                  /tmp/ssh-qgFBji4276/agent.4276

~ $ echo PWD
PWD
~ $ echo pwd
pwd
~ $ pwd

Path
----
C:\Users\zenobius

~ $ echo $Env:pwd
~ $ echo $Env:PWD
~ $ echo $PWD

Path
----
C:\Users\zenobius

~ $ gci env:pwd
gci : Cannot find path 'pwd' because it does not exist.
At line:1 char:1
+ gci env:pwd
+ ~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (pwd:String) [Get-ChildItem], ItemNotFoundException
    + FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.GetChildItemCommand

~ $ gci env:PWD
gci : Cannot find path 'PWD' because it does not exist.
At line:1 char:1
+ gci env:PWD
+ ~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (PWD:String) [Get-ChildItem], ItemNotFoundException
    + FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.GetChildItemCommand

~ $

This is preventing me from sharing my $SSH_AUTH_SOCK at runtime into my containers.

friism commented 7 years ago

@airtonix maybe I'm missing something, but I don't see in your example where you invoke docker-compose?

If you have a simple reproducible test, please consider opening a separate issue with details.

airtonix commented 7 years ago

Just assume I am. (Because, indeed I am).

On Tue., 6 Dec. 2016, 02:17 Michael Friis, notifications@github.com wrote:

@airtonix https://github.com/airtonix maybe I'm missing something, but I don't see in your example where you invoke docker-compose?

If you have a simple reproducible test, please consider opening a separate issue with details.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/docker/compose/issues/1085#issuecomment-264888849, or mute the thread https://github.com/notifications/unsubscribe-auth/AADvKStX5XgZOG1KJDvXJ-2t5ie14-OCks5rFDH-gaJpZM4DsN6o .

dopry commented 7 years ago

@airtonix, then please provide an example of exactly what you're doing, so someone else can reproduce it and work on it. Please do it in a new issue so your issue doesn't get lost in the rest of the windows support universe. Please refer to this issue so people interested in windows support issues will be aware. Thanks.

docker / compose

Epic: Windows support #1085