8 ms·
Dotcloud becoming Docker
- megaman821 13y agoSo is Docker, Inc. going to provide orchestration for Docker containers in the future? Are they going to host private registries?
- Myrmornis 13y agoDocker shall not be distributed or downloaded to or in Cuba, Iran, North Korea, Sudan or Syria This statement occurs in the docker README[0]. If at all possible, one would want to keep such channeling of potentially offensive government policy out of an open source software project's public documentation. For one thing, there are many enthusiastic open source programmers residing in the above list of countries. The NOTICE[1] document explains that Like all software products that utilize cryptography, the export and use of Docker is subject to the U.S. Commerce Department's Export Administration Regulations (EAR) because it uses or contains cryptography (see http://www.bis.doc.gov/index.php/policy-guidance/encryption http://www.bis.doc.gov/index.php/policy-guidance/encryption). Certain free and open source software projects have a lightweight set of requirements, which can generally be met by providing email notice to the appropriate U.S. government agencies that their source code is available on a publicly available repository and making the appropriate statements in the README. I'm not familiar with seeing other open source projects from American organizations state that they may not be downloaded in the above list of countries. Is the use of cryptography in docker different in a way that makes the docker organization more at risk from legal challenges from the federal government in this regard, or are docker being anal and xenophobic in blithely displaying this notice? [0] https://github.com/dotcloud/docker/blob/master/README.md https://github.com/dotcloud/docker/blob/master/README.md [1] https://github.com/dotcloud/docker/blob/master/NOTICE https://github.com/dotcloud/docker/blob/master/NOTICE
- Nrsolis 13y agoThis is kinda a non-negotiable for them, isn't it? It's not like they suddenly decided to enforce the USG policy and make a big deal about it. IANAL, but it seems prudent to acknowledge that the crypto work was done in the USA and therefore falls under the export policy that ALL exportable software falls under. My company has to include this warning on its software and we even have two different versions (domestic and export) to deal with this issue. I know it's unpopular, but why make Docker answer for it? Take it up with the USG if it makes you that unhappy. Better yet, strip out all the non-exportable code, replace it with code written from outside the USA and presto-changes, you've solved a problem for the whole world.
- shykes 13y agoDocker maintainer here. I also hate having to put this in the README (and hate it even more each time someone from Iran offers to contribute... what a waste of talent and energy this policy creates!). But we triple-checked with our legal counsel and they confirmed it's the only way to stay unambiguously out of trouble. As un-tasteful as it is, it's better than causing unnecessary legal trouble for docker contributors down the road. If you're interested in the subject here's an edifying expose of the situation: http://harpers.org/blog/2013/08/andrew-cockburn-on-the-failure-and-ferocity-of-americas-sanctions-programs/ http://harpers.org/blog/2013/08/andrew-cockburn-on-the-failu...
- Myrmornis 13y agoHi, thanks for the answer! I suppose it would be possible, without impacting the legal protection afforded by the notice, to preface the notice with some language indicating that docker would prefer it not to appear in the README, e.g. "unfortunately, due to ...". But in any case, congratulations with all the momentum you've gathered and I'm looking forward to learning more about docker here.
- shykes 13y agoThat was the exact purpose of the introductory line "Brought to you courtesy of our legal counsel." :) Coincidentally we just tweaked the language to match Apache and OpenSSL. It's pretty similar, but doesn't specifically name countries - it just refers to "whatever the rules happen to be under US regulation". https://github.com/dotcloud/docker/commit/b48fc9657976091ff3833d340877aa5b761e3969 https://github.com/dotcloud/docker/commit/b48fc9657976091ff3...
- darkarmani 13y agoThere is a small open source Linux distro called Fedora that has the same "xenophobic" and "offensive" notice. https://fedoraproject.org/wiki/Legal:Export https://fedoraproject.org/wiki/Legal:Export
- nickstinemates 13y agoAfter another legal review, there is another pull request open / probably part of 0.6.5 which changes the README to have language which the DSFG considers free.
- cschmidt 13y agoIf you're looking for the clickable version of the graphic on the OP (where the Read More links work), it is here: http://www.docker.com/about_docker/ http://www.docker.com/about_docker/
- slantview 13y agohello wowlrd! congrats!
- keeblus 13y agoDocker just keeps growing and growing. The amount of new businesses springing up to take advtange, along with some pretty heavy hitters looking to adopt, Docker has a fighting chance to become a standard from which everyone benefits.
- programminggeek 13y agoThis is a smart move. Some people might call it a pivot, but I think it's really doubling down on what people really want. dotCloud is not going to change the world (or make a truckload of money) by being Heroku's also-ran. Instead, they are taking something they built that is really interesting to a lot of people and building a business around it. As someone who is quite interested in docker, I'm glad that they are turning it into a real business. This benefits pretty much everyone who wants to see docker succeed. Also, it's really smart that they are keeping dotCloud alive. It would be incredibly irresponsible for them to kill that business just to push faster on docker.
- jbellis 13y agoI was with you until the last sentence. Why would it be irresponsible to kill the Heroku also-ran to push faster on what people really want?
- iand675 13y agoSometimes you have to build products that make enough intermediate revenue to get you to where you're trying to go.
- bmelton 13y agoBecause there are people running businesses on dotCloud currently? Because, at least in my humble opinion, it's actually better than Heroku? Because, at a minimum, cutting it off at the knees would engender tons and tons of bad will amongst their current customers? Because the customers deserve a couple of 'writing on the wall' style posts like this to begin thinking about migrating to alternatives before the cutoff is actually announced, forcing their hand in what could be 'too short a time period' to get migrated? The more time they buy their existing customers before dismantling what works, and what people are paying them for, the better. That said, this is the 'writing on the wall' that people should be looking for alternatives, at the barest minimum.
- mst 13y agoIt may not be the writing on the wall, since running a docker PaaS will be a useful way to understand ... what problems you encounter while running a docker PaaS. But we'll see, I guess.
- deleted 13y ago[deleted]
- sker 13y agoVMware is currently valued at 35B. Who is to say Docker couldn't be the next VMware? I would invest in these guys if I could.
- sciurus 13y agoMore likely Red Hat or someone else will buy them before that happens.
- jqueryin 13y agoCongratulations is well in order. It's so exciting to see the progress the team and platform have made in such a short amount of time. Only months ago at PyCon Solomon Hykes was showing off Docker to the public for the first time: http://www.youtube.com/watch?feature=player_embedded&v=wW9CAH9nSLs http://www.youtube.com/watch?feature=player_embedded&v=wW9CA...
- shykes 13y agoThanks! It has been a crazy ride, and it doesn't look like it's going to slow down any time soon!
- jxf 13y agoAs a user of Docker, I'm excited. But as someone who uses the dotCloud PaaS right now to run a company, I'm a little annoyed, mostly at myself for not seeing this coming. Clearly there's a diversion of resources away from the dotCloud PaaS to Docker, and that's going to have a toll somewhere. Despite the company's reassurances that everything is business as usual, I know that Docker [the project] is just too much of a beast and eventually the Docker [the company] will need to move on from the PaaS. (I should know, since I gave a talk about how "Docker is the future" just a few weeks after Docker was announced.) [0] I'm not really sure what my choices are now, either; DigitalOcean, I guess? I don't want to manage servers myself, and I want to be able to pay on the memory-usage axis for my app instances (which Heroku doesn't allow). I wasn't super excited by DO last year, but maybe things have changed. My current "light at the end of the tunnel" is hoping that the Docker-based PaaS ecosystem matures, but for now none of them seem like they're mature enough, and it's tough to keep up with all of them since it seems like another one pops up each week. Here's my wishlist: -- (1) command-line client for deployment via git repository and doing anything related to deployment (add new instances, remove instances, create new environments, assign domains to the PaaS router, etc.) -- (2) clear pricing -- (3) I can pay for more memory as I need it -- (4) ability to specify environment variables in a configuration file that take effect on the container process -- (5) web interface for administering the account Anyone have any recommendations? [0] http://spreecommerce.com/blog/spreeconf-DC-speaker-highlight-john-feminella http://spreecommerce.com/blog/spreeconf-DC-speaker-highlight...
- hrvbr 13y agoWindows Azure has the features you listed, although I'm not sure about #4. I too wanted a PaaS cloud, not an IaaS, and I found Azure to be the best option for my needs. I would have prefered a European company for legal reasons but there's no good one yet.
- yummyfajitas 13y agoThere are lots of hosting providers besides digitalocean - linode is a big one, so is joyent. I've been trying out digitalocean, but they make me nervous about reliability. Twice in 2 weeks I've gotten nonsensical abuse notifications (spamming, copyright infringement). One of the complaints was only 10 minutes after I spun up a droplet - my deploy script hadn't even finished. Makes me very nervous that DO will shut off all my droplets due to complaints about what the guy who previously owned the IP address did. MPAA-based failure is far harder to plan for than disk failure.
- ddorian43 13y agoCan't a PAAS use dedicated hosting and provide a cheaper price instead of the overcriped ec2 ? (is there one?)
- prottmann 13y agoI found today http://modulus.io http://modulus.io, they use different clouds. But definitly at a better price as dotcloud/nodejitsu/heroku, especially for smaller projects with SSL. Nice are the backend statistics without paying for any extra service. But i think in the next months many new PaaS services will rise, thanks to docker ;-) And i hope many new without amazon (amazon is not bad, but expensive).
- keeblus 13y agoI don't think it's too far off.
- Touche 13y agoIt's really interesting how Docker has become this beast, but was originally developed as a practical way to run their business. How many companies have been formed this way? It's an great thing to point to when a startup doesn't want to invest any time into getting their fundamental product right and just want to hack together using existing and known technologies.
- bmelton 13y agoIronically enough, in this case, Solomon originally started dotCloud as a tool to help manage server images, which he then leveraged into a business based on the tool, which now seems to be transitioning back to the tool itself as the core.
- deleted 13y ago[deleted]
- pron 13y agoCan someone please explain what is Docker exactly? I've read this page, http://www.docker.com/about_docker/docker/ http://www.docker.com/about_docker/docker/, and didn't understand. What exactly does it encapsulate? What does the application see when it queries its environment?
- ARothfusz 13y agoThis link does a more in-depth explanation: http://www.docker.io/the_whole_story/#Background http://www.docker.io/the_whole_story/#Background In general, Docker encapsulates and runs your processes and file systems in an exactly repeatable way, and in a format that you can replicate across a wide variety of machines.
- shrikrishna 13y agoThink about it as a very lightweight VM. You can do everything you can in a VM (which, in turn, can do everything you can in your regular system). Only thing is, it is a wrapper over lxc (Linux Containers) which means that you can only run Linux flavors and the host needs to have an advanced kernel (~3.8). Advantage is that if a VM needs ~80s to boot, a docker container can boot in <2s. And that's possible because a docker container shares the kernel of the host, (unlike VMs, which are all isolated)
- pron 13y agoOh, so it's not only a deployment mechanism, but an actual runtime "VM". What does it add over linux containers?
- keeblus 13y agoTechnically - Creation, management, communication, networking. Smartly. Ecosystem - more and more people every day are integrating with their tools, building business around Docker, or extending support of existing business to Docker.
- shykes 13y agoI gave some of my thoughts on the topic here: http://stackoverflow.com/questions/17989306/what-does-docker-add-to-just-plain-lxc http://stackoverflow.com/questions/17989306/what-does-docker...
- shykes 13y agoHey everyone, dotCloud/Docker founder here. I just wanted to thank the HN community for your support. Your feedback - both positive and negative - has shaped Docker more than you know. I also want to confirm that, yes, the trust and satisfaction of our customers matters more to us than any amount of money. You can always make more money later, but once trust is gone, it's gone. So expect us to work ourselves to exhaustion to continue to earn the trust of our paas customers, no matter how crazy things get with Docker (and I can tell you it's only going to get crazier!)
- jnwng 13y agoi remember how crazy it was at pycon 2013 when you all announced that you were open-sourcing docker... i'm so glad its working out! wish you all continued success.
- uxwtf 13y agoCongrats! This pivot was really successful for the company.
- shykes 13y agoAnd if you prefer to learn by practice, here's an awesome online tutorial: https://www.docker.io/gettingstarted/ https://www.docker.io/gettingstarted/
- shrikrishna 13y agoI have been using Docker for a couple of days now, and am really in love with it! Congratulations on the new direction and wish you all the luck in the world! I'd like to ask one question though - It seems that it's possible to limit the amount of cpu and memory of each container, but not so with the filesystem. I know this is some issue related to AUFS being used internally. But I would really like to know whether there is _any_ hack that allows us to limit the size of the filesystem, or whether it's in the pipeline?
- shykes 13y agoThere is definitely a hack :) You should join the #docker channel on irc (freenode) and ask for keeb or jpetazzo, they can help you out. If they don't, someone else probably will. People are very nice and useful there.
- keeblus 13y agoYep, as shykes says, I'm always available to help. Take a look at how I built tryrethink.info (which covers this topic and more) -> http://nick.stinemat.es http://nick.stinemat.es
- shrikrishna 13y agoThanks! That was really helpful!
- jpetazzo 13y ago> [is there] _any_ hack that allows us to limit the size of the filesystem? Docker 0.7 will let you do that, since each container will have its own (thin) block device, and therefore have a default size limit (which can be trivially bumped up if needed, of course). Now to anticipate your next question (assuming it is "when will Docker 0.7 be available?"), the answer would be "pretty soon", since the core team is ironing out the last issues before merging to master and releasing :-)
- deleted 13y ago[deleted]