5 ms·

Sorry if this is obvious somewhere, but i have to ask: Will this allow me on windows to pull a linux-based image (ubuntu for example) and run it on the windows

Sorry if this is obvious somewhere, but i have to ask: Will this allow me on windows to pull a linux-based image (ubuntu for example) and run it on the windows platform or pull a windows based image and run it on the linux docker platform host?

nickstinemates 12y ago
> Will this allow me on windows to pull a linux-based image (ubuntu for example) and run it on the windows platform You can do this today with boot2docker (running a linux VM behind the scenes) > pull a windows based image and run it on the linux docker platform host? I suppose the opposite of what I said could be true using something like KVM, but not a use case we are seeing a lot of right now.
- mbreese 12y ago
  If this is all a wrapper around boot2docker, everyone will be very disappointed... I highly doubt this is what the original question was about.
  - nickstinemates 12y ago
    It is not (a wrapper around b2d;) I tried to answer the specific question asked instead of guessing what the question is. The goal is: Package your Windows app in a docker container, use same tooling you would otherwise use to deploy to a docker engine running on a Windows host Package your Linux app in a docker container, use same tooling you would otherwise use to deploy to a docker engine running on a Linux host.
    - BinaryIdiot 12y ago
      Is the mix of that true as well? Package your Windows app in a docker container, use same tooling you would otherwise use to deploy to a docker engine running on a Linux host and vice versa? If not initially is that an ultimate goal?
      - nickstinemates 12y ago
        You can do that with VMs + Docker today. There are no current goals to make Linux executables run natively in windows and vice versa.
        BinaryIdiot 12y ago
        Ah okay thanks. The partnership sounds great and I know it's really freaking challenging but I hope in the future to see: 1. Native Mac OS X support (so Mac Apps can also be in containers) 2. Being able to mix container operating systems with other host operating systems. If that ever happens then operating systems and their versions would pretty much no longer matter; you could run anything anywhere without compatibility issues. I feel like this is something that has to eventually happen no matter what I'm just always curious what form(s) it will take.
        nickstinemates 12y ago
        > 1. Native Mac OS X support (so Mac Apps can also be in containers) Are there Mac servers out there you want to run apps on? Or just consumer apps you want to run on your mac? Curious about the use case! > Being able to mix container operating systems with other host operating systems. VMs are that abstraction today. I think we can do better going forward, but still a lot to do with what we currently have planned.
        BinaryIdiot 12y ago
        > Are there Mac servers out there you want to run apps on? Or just consumer apps you want to run on your mac? Curious about the use case! Maybe they haven't but I feel like Apple has abandoned the Mac OS X Server so no apps at least for me in that case but I think consumer apps would be a pretty cool use case. > VMs are that abstraction today. I think we can do better going forward, but still a lot to do with what we currently have planned. Roger; thanks!
        72deluxe 12y ago
    - throwaway1979 12y ago
      I'm also a bit confused. Let me give you a specific scenario. I have a windows .net application that works with windows 8 (no gui - some server side stuff). Can I package this up as a container and run this on a linux machine that has docker?
      - 4ad 12y ago
        Of course not.
      - nickstinemates 12y ago
        That is not currently a goal. It's the goal that you can tell docker - run this application, and it will find (or create!) a suitable host to run it on.
    - mbreese 12y ago
      Right... what the problem was is that you started seeing people get confused about running Linux containers on Windows and vice-versa. Hence all the questions around that... I guess that wasn't as clear from the announcement as it could have been. One of the main reasons is probably that the people that have been using Docker are Linux folks and aren't necessarily as familiar with deploying Windows-based applications.
      - nickstinemates 12y ago
        This is great feedback, thank you.
    - echion 12y ago
      I'm still unclear as to whether the linux apps can be deployed to a docker engine running on a windows host, and, vice-versa, whether docker windows containers can be run on a linux host. The announcement seemed to be clear that both of these are the goal. But your GP post https://news.ycombinator.com/item?id=8458603 https://news.ycombinator.com/item?id=8458603 causes me to doubt. Is there a missing comma in each sentence of the goal? It seems like there should be one after "use" or after "engine": 1) [after "use"] Package [on a Windows client] your Windows app in a docker container, use same tooling you would otherwise use [on a linux client], to deploy to a docker engine running on a Windows host Package [on a Windows client] your Linux app in a docker container, use same tooling you would otherwise use [on a linux client], to deploy to a docker engine running on a Linux host. 2) [after "use"] Package your Windows app in a docker container, use same tooling you would otherwise use to deploy to a docker engine [running on Windows or Linux], running [the packaging step] on a Windows host Package your Linux app in a docker container, use same tooling you would otherwise use to deploy to a docker engine [running on Windows or Linux], running [the packaging step] on a Linux host. I added the implications I understood to highlight the difference the comma placement makes. If there is no comma it's pretty ambiguous / confusing to me on which platform the docker engine is running. I believe from this post of yours that I have misunderstood the announcement, and that windows apps will be able to be made into docker containers that can only run on windows docker engines.
      - nickstinemates 12y ago
        > I believe from this post of yours that I have misunderstood the announcement, I'm sorry to hear that, we will work to do better. > and that windows apps will be able to be made into docker containers that can only run on windows docker engines. This is correct. There's also a thread on how, to the user of docker who just wants to `docker run` something, the distinction doesn't really matter in the end
      - cpuguy83 12y ago
        No, you will not be able to deploy a Linux app onto a Windows container, or vice-versa. Containers share a kernel, this would make it impossible. However, with things like boot2docker (25MB Linux distro), this makes it really leight-weight/easy to deploy into a VM and run that way.
  - johngossman 12y ago
    It's definitely not a wrapper around boot2docker. It's the kernel work etc. to enable native Windows containers running on Windows Server. No VMs need apply. That said, we're also working with Docker on the future of the boot2docker concept so that it easy to work with Linux-based Docker images from a Windows laptop, but that's just tuning the experience.

nickstinemates 12y ago

> Will this allow me on windows to pull a linux-based image (ubuntu for example) and run it on the windows platform You can do this today with boot2docker (running a linux VM behind the scenes) > pull a windows based image and run it on the linux docker platform host? I suppose the opposite of what I said could be true using something like KVM, but not a use case we are seeing a lot of right now.

mbreese 12y ago
If this is all a wrapper around boot2docker, everyone will be very disappointed... I highly doubt this is what the original question was about.
- nickstinemates 12y ago
  It is not (a wrapper around b2d;) I tried to answer the specific question asked instead of guessing what the question is. The goal is: Package your Windows app in a docker container, use same tooling you would otherwise use to deploy to a docker engine running on a Windows host Package your Linux app in a docker container, use same tooling you would otherwise use to deploy to a docker engine running on a Linux host.
  - BinaryIdiot 12y ago
    Is the mix of that true as well? Package your Windows app in a docker container, use same tooling you would otherwise use to deploy to a docker engine running on a Linux host and vice versa? If not initially is that an ultimate goal?
    - nickstinemates 12y ago
      You can do that with VMs + Docker today. There are no current goals to make Linux executables run natively in windows and vice versa.
      - BinaryIdiot 12y ago
        Ah okay thanks. The partnership sounds great and I know it's really freaking challenging but I hope in the future to see: 1. Native Mac OS X support (so Mac Apps can also be in containers) 2. Being able to mix container operating systems with other host operating systems. If that ever happens then operating systems and their versions would pretty much no longer matter; you could run anything anywhere without compatibility issues. I feel like this is something that has to eventually happen no matter what I'm just always curious what form(s) it will take.
        nickstinemates 12y ago
        > 1. Native Mac OS X support (so Mac Apps can also be in containers) Are there Mac servers out there you want to run apps on? Or just consumer apps you want to run on your mac? Curious about the use case! > Being able to mix container operating systems with other host operating systems. VMs are that abstraction today. I think we can do better going forward, but still a lot to do with what we currently have planned.
        BinaryIdiot 12y ago
        > Are there Mac servers out there you want to run apps on? Or just consumer apps you want to run on your mac? Curious about the use case! Maybe they haven't but I feel like Apple has abandoned the Mac OS X Server so no apps at least for me in that case but I think consumer apps would be a pretty cool use case. > VMs are that abstraction today. I think we can do better going forward, but still a lot to do with what we currently have planned. Roger; thanks!
        72deluxe 12y ago
  - throwaway1979 12y ago
    I'm also a bit confused. Let me give you a specific scenario. I have a windows .net application that works with windows 8 (no gui - some server side stuff). Can I package this up as a container and run this on a linux machine that has docker?
    - 4ad 12y ago
      Of course not.
    - nickstinemates 12y ago
      That is not currently a goal. It's the goal that you can tell docker - run this application, and it will find (or create!) a suitable host to run it on.
  - mbreese 12y ago
    Right... what the problem was is that you started seeing people get confused about running Linux containers on Windows and vice-versa. Hence all the questions around that... I guess that wasn't as clear from the announcement as it could have been. One of the main reasons is probably that the people that have been using Docker are Linux folks and aren't necessarily as familiar with deploying Windows-based applications.
    - nickstinemates 12y ago
      This is great feedback, thank you.
  - echion 12y ago
    I'm still unclear as to whether the linux apps can be deployed to a docker engine running on a windows host, and, vice-versa, whether docker windows containers can be run on a linux host. The announcement seemed to be clear that both of these are the goal. But your GP post https://news.ycombinator.com/item?id=8458603 https://news.ycombinator.com/item?id=8458603 causes me to doubt. Is there a missing comma in each sentence of the goal? It seems like there should be one after "use" or after "engine": 1) [after "use"] Package [on a Windows client] your Windows app in a docker container, use same tooling you would otherwise use [on a linux client], to deploy to a docker engine running on a Windows host Package [on a Windows client] your Linux app in a docker container, use same tooling you would otherwise use [on a linux client], to deploy to a docker engine running on a Linux host. 2) [after "use"] Package your Windows app in a docker container, use same tooling you would otherwise use to deploy to a docker engine [running on Windows or Linux], running [the packaging step] on a Windows host Package your Linux app in a docker container, use same tooling you would otherwise use to deploy to a docker engine [running on Windows or Linux], running [the packaging step] on a Linux host. I added the implications I understood to highlight the difference the comma placement makes. If there is no comma it's pretty ambiguous / confusing to me on which platform the docker engine is running. I believe from this post of yours that I have misunderstood the announcement, and that windows apps will be able to be made into docker containers that can only run on windows docker engines.
    - nickstinemates 12y ago
      > I believe from this post of yours that I have misunderstood the announcement, I'm sorry to hear that, we will work to do better. > and that windows apps will be able to be made into docker containers that can only run on windows docker engines. This is correct. There's also a thread on how, to the user of docker who just wants to `docker run` something, the distinction doesn't really matter in the end
    - cpuguy83 12y ago
      No, you will not be able to deploy a Linux app onto a Windows container, or vice-versa. Containers share a kernel, this would make it impossible. However, with things like boot2docker (25MB Linux distro), this makes it really leight-weight/easy to deploy into a VM and run that way.
- johngossman 12y ago
  It's definitely not a wrapper around boot2docker. It's the kernel work etc. to enable native Windows containers running on Windows Server. No VMs need apply. That said, we're also working with Docker on the future of the boot2docker concept so that it easy to work with Linux-based Docker images from a Windows laptop, but that's just tuning the experience.