5 ms·

Just curious, how are people building Docker images these days? Doesn't it only run on 64-bit Linux? I have a 32 bit Linux desktop and a Mac and haven't gotte

by chubot 13y ago

Just curious, how are people building Docker images these days? Doesn't it only run on 64-bit Linux? I have a 32 bit Linux desktop and a Mac and haven't gotten around to installing Docker. At work I have a 64 bit Linux desktop and it seemed to be extremely picky about the kernel version so I gave up. Are people running Linux VMs on their Macs to build containers? I like the idea of this service. But both the client side and the server side have to be easy. Unless I'm missing something it seems like they made the server side really easy, but the client side is still annoying.

dekz 13y ago
I'm building docker images on 64-bit linux (ubuntu) and maintaining a repo of Dockerfiles, instead of uploading to the docker repository. You need a recent version of the linux kernel that supports Linux Containers. It's best if you can run Ubuntu 13 somewhere. > Are people running Linux VMs on their Macs to build containers? FreeBSD supports jails which are similar to linux containers in a way, but OSX does not. So unfortunately you're going to have to run a VM, checkout vagrant and docker though. [1] [1]: http://docs.docker.io/en/latest/installation/vagrant/ http://docs.docker.io/en/latest/installation/vagrant/
- TheMakeA 13y ago
  OSX has seatbelts[1], which is similar to jails. They are just clunky and not documented. Chrome uses them for sandboxing browser processes[2]. [1] https://developer.apple.com/library/mac/documentation/Darwin/Reference/ManPages/man1/sandbox-exec.1.html https://developer.apple.com/library/mac/documentation/Darwin... [2] http://www.chromium.org/developers/design-documents/sandbox/osx-sandboxing-design http://www.chromium.org/developers/design-documents/sandbox/...
  - wmf 13y ago
    No amount of jails or seatbelts is going to allow you to run a Linux executable on a Darwin kernel, though.
Lazare 13y ago
Yes. Emerging best practices seems to be to use Vagrant to create a great development environment, then use docker containers inside that for isolation. The two work together quite well. There's a comment from the Vagrant creator here about that: https://news.ycombinator.com/item?id=6291549 https://news.ycombinator.com/item?id=6291549 In short, yes, just run a VM.
- chubot 13y ago
  So I already use Linux almost exclusively for development, and VMs are not in my workflow at all. It seems bizarre to build a VM to build a container! Like too many levels of yak shaving.
  - TheMakeA 13y ago
    All of my projects now include a Vagrantfile. It makes managing dependencies and creating repeatable environments simple. The work flow is: $ vagrant up $ vagrant ssh Editing and committing changes take place on the host. Running servers, tests, building Docker containers, etc, takes place on the guest. You can get a new device ready for hacking on a project in minutes. Just git clone, vagrant up, grab a quick coffee. I would definitely recommend putting VMs in your work flow.
    - shykes 13y ago
      The dominant workflow in docker-land is to ditch the Vagrantfile, use a Dockerfile instead, and sometimes use Vagrant when it helps you get a VM up and running with docker on it (but that Vagrantfile is typically the same across all projects requiring docker).
  - Lazare 13y ago
    > It seems bizarre to build a VM to build a container! Like too many levels of yak shaving. Perhaps, but you just said: > I have a 32 bit Linux desktop and a Mac and haven't gotten around to installing Docker. At work I have a 64 bit Linux desktop and it seemed to be extremely picky about the kernel version so I gave up. Precisely. Hence VMs, because Vagrant makes it trivial to spin up an instance configured however you like. You're basically saying "I have a problem installing Docker, but I don't need a VM because I don't have any problems a VM would solve", but this is nonsense because this is the precise problem development VMs are meant to solve.

by chubot 13y ago

dekz 13y ago

I'm building docker images on 64-bit linux (ubuntu) and maintaining a repo of Dockerfiles, instead of uploading to the docker repository. You need a recent version of the linux kernel that supports Linux Containers. It's best if you can run Ubuntu 13 somewhere. > Are people running Linux VMs on their Macs to build containers? FreeBSD supports jails which are similar to linux containers in a way, but OSX does not. So unfortunately you're going to have to run a VM, checkout vagrant and docker though. [1] [1]: http://docs.docker.io/en/latest/installation/vagrant/ http://docs.docker.io/en/latest/installation/vagrant/

TheMakeA 13y ago
OSX has seatbelts[1], which is similar to jails. They are just clunky and not documented. Chrome uses them for sandboxing browser processes[2]. [1] https://developer.apple.com/library/mac/documentation/Darwin/Reference/ManPages/man1/sandbox-exec.1.html https://developer.apple.com/library/mac/documentation/Darwin... [2] http://www.chromium.org/developers/design-documents/sandbox/osx-sandboxing-design http://www.chromium.org/developers/design-documents/sandbox/...
- wmf 13y ago
  No amount of jails or seatbelts is going to allow you to run a Linux executable on a Darwin kernel, though.

Lazare 13y ago

Yes. Emerging best practices seems to be to use Vagrant to create a great development environment, then use docker containers inside that for isolation. The two work together quite well. There's a comment from the Vagrant creator here about that: https://news.ycombinator.com/item?id=6291549 https://news.ycombinator.com/item?id=6291549 In short, yes, just run a VM.

chubot 13y ago
So I already use Linux almost exclusively for development, and VMs are not in my workflow at all. It seems bizarre to build a VM to build a container! Like too many levels of yak shaving.
- TheMakeA 13y ago
  All of my projects now include a Vagrantfile. It makes managing dependencies and creating repeatable environments simple. The work flow is: $ vagrant up $ vagrant ssh Editing and committing changes take place on the host. Running servers, tests, building Docker containers, etc, takes place on the guest. You can get a new device ready for hacking on a project in minutes. Just git clone, vagrant up, grab a quick coffee. I would definitely recommend putting VMs in your work flow.
  - shykes 13y ago
    The dominant workflow in docker-land is to ditch the Vagrantfile, use a Dockerfile instead, and sometimes use Vagrant when it helps you get a VM up and running with docker on it (but that Vagrantfile is typically the same across all projects requiring docker).
- Lazare 13y ago
  > It seems bizarre to build a VM to build a container! Like too many levels of yak shaving. Perhaps, but you just said: > I have a 32 bit Linux desktop and a Mac and haven't gotten around to installing Docker. At work I have a 64 bit Linux desktop and it seemed to be extremely picky about the kernel version so I gave up. Precisely. Hence VMs, because Vagrant makes it trivial to spin up an instance configured however you like. You're basically saying "I have a problem installing Docker, but I don't need a VM because I don't have any problems a VM would solve", but this is nonsense because this is the precise problem development VMs are meant to solve.