menu
Channels
Team

clarify future support of docker on now platform

November 8, 2018 at 6:21pm

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'; @rauchg would you kindly clarify this?

Show previous messages

November 9, 2018 at 3:11pm

Thing is I don't even want to have to SSH into a VM

  • reply
  • like
like-fill
1
  • reply
  • like

nvm, no real native support for scalingo, maybe https://devcenter.heroku.com/articles/build-docker-images-heroku-yml heroku then..

  • reply
  • like

Well.... no more Docker on now is terrible news, at least I see I am not the only one who thinks that. Not everybody likes Lambdas, and Lambdas are not suitable for all use cases. As much as I like Now 1.0. if this decision stands, I am starting to look for alternatives tomorrow.

like-fill
5
  • reply
  • like

Did anyone try Hyper.sh ? they seem to embrace the Docker UX

  • reply
  • like

I have tried Hyper.sh - although it is close to Now, I liked it much less. But given the docker ban, it might be a good fallback option.

like-fill
1
  • reply
  • like

I have tried Hyper.sh - although it is close to Now, I liked it much less. But given the docker ban, it might be a good fallback option.

Well considering we rely a lot on Docker, it seems the only solution available for us :(

  • reply
  • like

Thx for sharing this, it looks like an alternative to hyper.sh

like-fill
1
  • reply
  • like

Scalingo is also not "direct docker hosting" as I just found out. They are also "app hosting" and they have docker behind the scenes, and a "docker addon", which I am not sure what is it for, but as I saw the 50 euro per month price tag, I realized it is a waste of time (seems like more of a Heroku clone, then a Now clone).

Edited
like-fill
1
  • reply
  • like

We've been planning to migrate a REST API with multiple endpoints to Now which is written in Python with Falcon. But with Now v2, this seems to become an issue unless we want to integrate with the http package provided by Now's Python runtime. As far as I understand it, each endpoint would become an individual AWS Lambda and routing would be specified in now.json, right? With Docker it would have been a breeze to deploy on Now. I don't understand the decision to go away from user-provided Dockerfile-based deployment.

like-fill
3
  • reply
  • like

I didn't realize this thread was happening here and was commenting on HN, but here are my thoughts. I am sure there are business, strategy or technical reasons for Zeit to announce this, but I hope they reconsider the support for Serverless Docker.

I work for a large media organization and we recently subscribed to a paid account and I have been moving over many of our internal projects like prototypes, design systems, vendor collaboration projects over to now. Now 1.0 is an awesome place to host these projects and possibly, we could have used Now in future for graduating some of our consumer facing projects. Currently, all our consumer facing projects are launched on our standardized AWS/Fastly infrastructure, where we have support for VMs, Containers and Lambdas.

The primitives of Docker are more standardized and cross-platform enough to support the above workflow. Using npm builders from @now isn't practical for us. Even though we are heavy node users, we are unlikely to switch over to serverless paradigm for many of our workloads anytime soon. Like others mentioned, it is certainly a no go for many of our PHP and Java projects. Additionally, using the now builders is a lock-in from our standpoint that we want to avoid.

I think if the Serverless Docker option will continue to be available in future, it makes sense for us to continue investing in Now based workflows. I am not a fan of using the alternatives in the form of AWS Fargate or equivalents from GCP or Azure

like-fill
15
  • reply
  • like

I truly love you guys, but the decision to abandon Docker is just killing me. I get when you say things like "We have no intention of shutting Now v1 down any soon". But announcing something like this in the way you did is just leaving me gutted.

I know not all customers are going to like product decisions. Sometimes you need to alienate a few customers to appeal to a broader audience. I do think we deserve a little more explanation and reasoning behind this decision. I mean @matheus and @rauchg here you guys were in April standing on stage and advocating a Docker first strategy with such a passion and commitment. Now 8 months later you are ready to move docker to legacy system. I mean... what happend here?

When a company moves to a relatively new service, it often a big deal. Lots of stakeholders need to convinced and pros and cons are endlessly debated. There are always a lot of naysayers who want to invest in a more "proven technology"... well today I just feel like I just got a big reality check.

Love what @daniel-gimenes said: "I think the biggest flaw here was the naming of Now 2.0 and how you presented it".

I think there should be a future for containers under Now. What I would suggest is to keep v1.0 under the "Now Docker" product name and move v2.0 under the "Now Lambda" name. I think having both options available can be awesome going forward. Spin up a quick Lambda to get some small project going. Use a container for a more complex setup where a simple builder isn't going to cut it. I think that would be cool.

Anyway thats my suggestion, hope you guys have a few minutes for a long time supporter.

Edited
like-fill
28
  • reply
  • like

I completely agree with @dvdm Having both "Now Docker" and "Now Lambda" as options would be awesome

like-fill
20
  • reply
  • like

I might give DigitalOcean One-Click Docker deploy a try...

Check out their new Kubernetes offering. its pretty great and super cheap. They offer the master free so you only pay for nodes which can be their small $5 1gb instances. Its what i'm utilizing now that Docker is being phased out on now.

like-fill
4
  • reply
  • like

I'm trying Azure Pipeline right now, the assistant auto detected my Dockerfile, got a green build with webpack build, docker build (nginx) and e2e tests without even looking at the doc (yet) still have to (auto) deploy it, but native dockerfile support is there, so far I had to do 0 modification to my application code

like-fill
2
  • reply
  • like

Have you guys seen (https://zeit.co/docs/v2/platform/upgrade-to-2-0):

NOTE: v1 is fully maintained and supported. We will only announce a deprecation date once we have ensured all our customers workloads are migrated and the tooling is in place for a smooth transition.

So v1 is destined to end at some point.

  • reply
  • like

How about Apollo Stack with graphql subscription ? My realtime infrastructure is built on it. Even the escape hatch is Docker is soon abandoned here. So frustrated on NOW !

  • reply
  • like

It would be really great if someone from the Zeit team could comment on this issue. reading through this thread there are several use cases that just don’t align well with the lambda model and even if now‘s stance is that this is the way forward it would only be fair to people in need of other use cases to bring clearity if now will be a viable option for them in the future.

Edited
  • reply
  • like

I want to re-assure everyone that we are 100% confident that this is the right direction for the platform. We wouldn't call this 2.0 if I wasn't deeply convinced that is is the future of deployment and code execution.

like-fill
8
  • reply
  • like

It's true that *some* use cases are still not addressed, which is why we didn't just phase out v1. We are working on a lot of very exciting features, builders and integrations that I'm confident will make all your web applications work great on Now 2.0.

like-fill
4
  • reply
  • like

We have been exploring the tradeoff space between processes and functions, containers and lambdas, for a long time. We understand the problem extremely well, and we have seen and learned first hand what scales and what doesn't.

like-fill
4
  • reply
  • like

@rauchg Are you planning to support deployment of, e.g., web services with multiple endpoints, implemented e.g. with Python Flask, without making changes to the code?

  • reply
  • like

@raucgh How about websocket over lambda ? I would be happy to refactor a monothlic to lambda, as soon as it supports websocket connection. Thanks.

like-fill
2
  • reply
  • like

@sisp we are investing quite a bit into our Python builder right now, as a matter of fact. We have a lot of good news coming for the python community :)

like-fill
2
  • reply
  • like
Show more messages
private
This conversation has been locked