5 ms·

That was my thought as well. Docker not supporting a version for longer than a year is a no-go. This is not enterprise ready. It's barely dev ready because my

by AckSyn 10y ago

That was my thought as well. Docker not supporting a version for longer than a year is a no-go. This is not enterprise ready. It's barely dev ready because my devs need a stable environment to work in, not something that's going to puke every few weeks.

todd3834 10y ago
Just because something isn't guaranteed not to puke every few weeks doesn't mean that it will. I've been using Docker for a while now and it has been very rare that I run into issues because of an update.
- jsudhams 10y ago
  In large enterprise it will take 6 months to get a version certified to work with tooling so need 3 year at the minimum to put any effort on it.
  - IMTDb 10y ago
    Docker initial release was just 4 years ago, your asking for a support timeframe that's around the same length as the age of the project itself. Docker still is a new product, evolving very fast (this announcement is just one more proof of that). Is it production ready ? Yes If you want to move fast and benefit from new tech and are ready to upgrade regularly. No if you are not able to perform those upgrades and need insurance that the project will contribute significant ressources to fixing issues on 3 years old versions. And currently I totally understand that the Docker team sets slider more towards "new dev" than towards "support". That will probably change in the future.
    - AckSyn 10y ago
      > Docker still is a new product, evolving very fast And that's a large part of the problem. We, as an Enterprise, don't want something with rapid evolving infrastructure, features. We need stability, critical and security patches. Emphasis on stability. 3 years is a minimum we would consider for that and not a 1 year only support range.
      - djb_hackernews 10y ago
        You just listed a bunch of reasons why your Enterprise should not be using Docker. EDIT: I did not realize it was per node pricing. I take back mostly everything I said below. I hope that ultimately when Docker does provide 3 years of support, you'll be willing to pay up. Look at the pricing, even the biggest Enterprise plan is $2000/yr. This is aimed at small consultancies, startups and small businesses, etc that are tired of sending their developers into the docker github issues to log bugs and argue features. When Docker adds a plan that satisfies your Enterprise, you'll be paying typical Enterprise prices that will be at least an order of magnitude larger than the current biggest plan. Hopefully you are able to put your money where your mouth is.
        amouat 10y ago
        Note that the pricing is per node.
        shykes 10y ago
        For reference here are a few case studies of enterprises using Docker EE in production: - https://www.docker.com/customers/docker-datacenter-delivers-security-and-scale-adp https://www.docker.com/customers/docker-datacenter-delivers-... - https://www.docker.com/customers/ge-uses-docker-enable-self-service-their-developers https://www.docker.com/customers/ge-uses-docker-enable-self-... - https://www.docker.com/customers/ing-delivers-value-customers-faster https://www.docker.com/customers/ing-delivers-value-customer... There are many more here: https://www.docker.com/customers https://www.docker.com/customers Also, as others have noted: the price point is per-node. Docker EE is most definitely for enterprises.
        jacques_chester 10y ago
        Of interest, GE is a Cloud Foundry Foundation member and a founding investor in Pivotal. They have a fairly engineering org working on their IoT-oriented version, Predix. Disclosure: I work for Pivotal, etc.
      - IMTDb 10y ago
    - vacri 10y ago
      NodeJS still is a new product, evolving very fast. Is it production ready ? Yes If you want to move fast and benefit from new tech and are ready to upgrade regularly. ... ... and NodeJS learned that if you want to be a proper production environment, you still need to have LTS. 'Being fashionable' isn't enough. > And currently I totally understand that the Docker team sets slider more towards "new dev" than towards "support". Flashy features built on an unstable base is not something you want to stake a company on - support is important, it's just not sexy. New features gets you new users. Support makes them stay... and even pay.
  - Turbots 10y ago
    Guess you're not working in a very agile company. Enjoy your bankruptcy soon.
- imglorp 10y ago
  There are 2250 open issues on the github. We're tracking a good handful or two as nuisances to our process but there are no showstoppers for us in dev. We're not in production yet. https://github.com/docker/docker/issues https://github.com/docker/docker/issues
- majewsky 10y ago
  We had a pretty good time with CoreOS ^W Container Linux by CoreOS in that regard. They seem to be really good at providing automatic OS updates and shipping known-to-be-working combinations of kernel and Docker.
- piva00 10y ago
  I've been working with Docker in production for about 2 years now and I have the opposite experience, not in the sense that I run in issues very very frequently between updates but it's happened often enough for us to not push updates at all for Docker until we are very confident it won't break. It's happened at least 5 times in the past 2 years, that's VERY frequent from an enterprise viewpoint.
deleted 10y ago
[deleted]

by AckSyn 10y ago

todd3834 10y ago

Just because something isn't guaranteed not to puke every few weeks doesn't mean that it will. I've been using Docker for a while now and it has been very rare that I run into issues because of an update.

jsudhams 10y ago
In large enterprise it will take 6 months to get a version certified to work with tooling so need 3 year at the minimum to put any effort on it.
- IMTDb 10y ago
  Docker initial release was just 4 years ago, your asking for a support timeframe that's around the same length as the age of the project itself. Docker still is a new product, evolving very fast (this announcement is just one more proof of that). Is it production ready ? Yes If you want to move fast and benefit from new tech and are ready to upgrade regularly. No if you are not able to perform those upgrades and need insurance that the project will contribute significant ressources to fixing issues on 3 years old versions. And currently I totally understand that the Docker team sets slider more towards "new dev" than towards "support". That will probably change in the future.
  - AckSyn 10y ago
    > Docker still is a new product, evolving very fast And that's a large part of the problem. We, as an Enterprise, don't want something with rapid evolving infrastructure, features. We need stability, critical and security patches. Emphasis on stability. 3 years is a minimum we would consider for that and not a 1 year only support range.
    - djb_hackernews 10y ago
      You just listed a bunch of reasons why your Enterprise should not be using Docker. EDIT: I did not realize it was per node pricing. I take back mostly everything I said below. I hope that ultimately when Docker does provide 3 years of support, you'll be willing to pay up. Look at the pricing, even the biggest Enterprise plan is $2000/yr. This is aimed at small consultancies, startups and small businesses, etc that are tired of sending their developers into the docker github issues to log bugs and argue features. When Docker adds a plan that satisfies your Enterprise, you'll be paying typical Enterprise prices that will be at least an order of magnitude larger than the current biggest plan. Hopefully you are able to put your money where your mouth is.
      - amouat 10y ago
        Note that the pricing is per node.
      - shykes 10y ago
        For reference here are a few case studies of enterprises using Docker EE in production: - https://www.docker.com/customers/docker-datacenter-delivers-security-and-scale-adp https://www.docker.com/customers/docker-datacenter-delivers-... - https://www.docker.com/customers/ge-uses-docker-enable-self-service-their-developers https://www.docker.com/customers/ge-uses-docker-enable-self-... - https://www.docker.com/customers/ing-delivers-value-customers-faster https://www.docker.com/customers/ing-delivers-value-customer... There are many more here: https://www.docker.com/customers https://www.docker.com/customers Also, as others have noted: the price point is per-node. Docker EE is most definitely for enterprises.
        jacques_chester 10y ago
        Of interest, GE is a Cloud Foundry Foundation member and a founding investor in Pivotal. They have a fairly engineering org working on their IoT-oriented version, Predix. Disclosure: I work for Pivotal, etc.
    - IMTDb 10y ago
  - vacri 10y ago
    NodeJS still is a new product, evolving very fast. Is it production ready ? Yes If you want to move fast and benefit from new tech and are ready to upgrade regularly. ... ... and NodeJS learned that if you want to be a proper production environment, you still need to have LTS. 'Being fashionable' isn't enough. > And currently I totally understand that the Docker team sets slider more towards "new dev" than towards "support". Flashy features built on an unstable base is not something you want to stake a company on - support is important, it's just not sexy. New features gets you new users. Support makes them stay... and even pay.
- Turbots 10y ago
  Guess you're not working in a very agile company. Enjoy your bankruptcy soon.
imglorp 10y ago
There are 2250 open issues on the github. We're tracking a good handful or two as nuisances to our process but there are no showstoppers for us in dev. We're not in production yet. https://github.com/docker/docker/issues https://github.com/docker/docker/issues
majewsky 10y ago
We had a pretty good time with CoreOS ^W Container Linux by CoreOS in that regard. They seem to be really good at providing automatic OS updates and shipping known-to-be-working combinations of kernel and Docker.
piva00 10y ago
I've been working with Docker in production for about 2 years now and I have the opposite experience, not in the sense that I run in issues very very frequently between updates but it's happened often enough for us to not push updates at all for Docker until we are very confident it won't break. It's happened at least 5 times in the past 2 years, that's VERY frequent from an enterprise viewpoint.

deleted 10y ago

[deleted]