menu

ZEIT

Our mission is to make cloud computing as easy and accessible as mobile computing. You can find our Next.js community here.

Channels
Team

clarify future support of docker on now platform

November 8, 2018 at 6:21pm
The ZEIT community has a new home. This thread is preserved for historical purposes. The content of this conversation may be innaccurrate or out of date. Go to new community home →

clarify future support of docker on now platform

November 8, 2018 at 6:21pm
It seems zeit is moving away from allowing customers to utilize Docker as a common 'primitive'; would you kindly clarify this?

November 8, 2018 at 6:22pm
This. I've been all over the docs, I chose zeit because they had first-class support for Dockerfile... not sure I like where this is going
like-fill
18
  • reply
  • like
The UX for people using Dockerfile is Halloween-style scary: banner all over the place with NO info on Docker deployments:
Edited
  • reply
  • like
  • reply
  • like
  • reply
  • like
  • reply
  • like
Sorry for the multiple messages, but I find the situation very confusing.
Edited
like-fill
1
  • reply
  • like
Would love some input on this as well.
like-fill
1
  • reply
  • like
Let's hope they reply soon.. IMO many users of now.sh are using Docker.. as it was marketed as a flagship feature
like-fill
8
  • reply
  • like
I apologize for the "aggressiveness" of the warnings/banners – they give a wrong impression.
To clarify a bit: we have no intention of shutting Now v1 down any soon. We will only start thinking about deprecation plans once we are able to accommodate the most common and critical use cases of v1 on v2. We'll be writing a lot more on the upgrade path, on how to adapt different use cases to the lambda world and so on.
like-fill
11
  • reply
  • like
Thanks for the reply. Any motivations regarding "not" supporting Docker in v2 (right away), I'm curious.
  • reply
  • like
I'm far from being a dev op specialist.. I'm really wondering.
  • reply
  • like
We will only start thinking about deprecation plans once we are able to accommodate the most common and critical use cases of v1 on v2.
This is rather unfortunate. It sounds like the writing is on the wall here... Docker support is going away and everything is moving to a Lambda based model. This seems too prescriptive to me... For ex, an express application to either:
- be fully wrapped in a Lambda (would anyone really do this in production?)
or
- have each route converted to a lambda (what's the story around shared middleware here, seems like a lot of new overhead is introduced)
Not to mention all the other use cases that don't fit in Lambda. :/
like-fill
6
  • reply
  • like
my original question is not answered. I have zero motivation to migrate from dockerfiles to the 'builder' abstraction mentioned in today's announcement. It would be appreciated if you gave users a transparent answer so they can plan accordingly.
like-fill
9
  • reply
  • like
yes, ultimately we do plan to remove Docker support. We thought a lot about containers for the past 3 years, analyzed thousands of use cases and spoke with thousands of customers, and we concluded that functions/lambdas are superior to containers for the vast majority of workloads.
We're already writing a blogpost with more details on our thinking, reasoning and conclusions 👍
like-fill
12
  • reply
  • like
I'm very interested to hear the proposed solution for loops/jobs that is hinted at in the new Now v2 docs. It's hard for me to judge this new direction until "the rest" of the features are released. I would be open to the idea of refactoring my projects into this new approach but will have to wait and stay on v1 for now.
  • reply
  • like
Show more messages
private
This conversation has been locked
private
This channel has been archived