Spectrum is now read-only. Learn more about the decision in our official announcement.


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


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?
Show previous messages

November 10, 2018 at 3:40am
I'm not certain, at this point, if my entire app that I've built on express and FeathersJS would ever jive with serverless architecture. I feel it'd be a major rewrite.
have you guys tried kubernetes? I got a kubernetes cluster setup in Google Cloud and now I just push docker images to it and it will host it for me
I use Kubernetes on Google Cloud
I don't get it. So with Docker, I can write and app, put it on now, or Digital Ocean, or if the client demands it, run Docker on their physical server in office, or unwrap what is in the Docker container and run it the old way on a real machine without the container...
With the new Now Lambda, I cannot do that. It will be suck require it to be hosed on NOW's platform. Surely, I can move it around on the cloud provider you guys support (AWS, GCE), but there is no way to deploy it to other standalone server / computers?
I was referring to the idea that if there was some sort of wrapper that turns my plain Python Flask app into a Now-compatible web app, i.e. it analyzes the routes in my Flask app and "magically" exposes each route as a standalone function that can be served through Lambda, then I'd write my Flask app as always, write a Dockerfile as always for on-premise (or generally non-Now) deployment, and deploy it on Now with the wrapper. is the closest to the (old-) Now model, but as far as I know they require you to have an image stored in some registry before you can launch it there.
I get the idea and even though i wont go in that direction your expertise is propably right that this is the cheapest and best way to move forward. But however good it might be, it is still a lockin. It does not matter that i can choose where to distribute it behind the scenes. I can move a docker setup to wherever i want, even my own servers if i need to. With the new v2 this is a different story, it sounds way more locked in. And i kind of lost a good amount of trust atm. Maybe thats unfair and i am wrong. Actually i hope i am wrong 😕
this is very concerning 🤔
this is very concerning 🤔
Ok guys - so I know it is not exactly polite to discuss other services in a chat that belongs to Zeit Now, but since Zeit is dressing nicely with its Lambda dress, for what I believe is a strategic move to get the attention of Amazon's acquisition team, and since it looks Docker will be gone forever from Now sometime soon, I feel obligated to share the results of my search for alternatives.
- : even though it shares similarities to Now, it is much less user friendly. You need to worry about IPs and instance sizes, and the deployment process is quite painful and long. I managed to make it work, sometimes. One huge downside, is the fact that you need to have a docker image in DockerHub. After playing with it I cannot recommend it as an alternative, but it may still appeal to some people I guess.
- Docker on Heroku : I am a long time user of Heroku, using non-containerized applications. I just tried deploying one of my docker test apps to Heroku, and it was very easy and smooth, and even free. If anyone of you decides to go that route, I hope to save you some time by saying this: The only change you probably need to do to your Dockerfile, is to ensure your `CMD` uses the `$PORT` environment variable. This is the variable provided by Heroku, and the `EXPOSE` directive is ignored by Heroku.
I have been using Docker in Google Cloud Container Service / Kubernetes, aside from the initial setup, everything has been flawless and I haven’t had any downtime in the last 3 months, pricewise, it is similar to Now v1
on demand version of now v1
How is the SSL configuration and aliasing of domains to instances? Those are things Now does quite well -- pretty easy to setup on GCP? I also feel a little bad discussing this on Zeit's forum, but it sounds like V2 won't fully do what V1 was capable of, so it's reasonable discussion to be had.
Looks like can be counted as an alternative. Any experience with this platform?
i think they just need to find a way to ”promote” the docket support of v1 into v2 so that the community knows we can count on Zeit to conti support Docker along side whatever cool and better stuff they are trying to push on it now. Given the current state of Docker and container hostings, i think Zeit will be missing out a lot should they decide to drop it completely.
back to your original question, right now I took the easy way and offer SSL support via cloudflare.
back to your original question, right now I took the easy way and offer SSL support via cloudflare.
and there is Lets Encrypt which also powers Now’s SSL...
but you won’t get Now’s seamless CDN and SSL on other providers
A quick look into Fargate pricing ( vCPU's are $0.0506/hr, memory is $0.0127/gb/hr. So, it's pretty expensive.
2.0 seems like it will fantastic for many things I’ll likely use it for things in the future, but like so many others I’m currently using a Docker deployment for a client‘s Rails app. It’s fairly complicated but Docker makes it super easy to deploy.
Please, please keep Docker as a first class deployment option on Now.
We know the benefits of Lamda, but what we all want to hear from you is that you will keep Docker support along with 2.0. Lambda will never be good for a Rails app and many other use cases.
We currently use now for an angular app. Thanks to the Github integration, every commit on a PR is built and deployed. Since we have git submodules, we use Docker to build the app. What is your recommandation to upgrade to v2? Replace the submodule by npm pointing to the github repo/commit?

November 11, 2018 at 12:04am
I was hoping to move my rails app (old, but still serving 3 million reqs/month) from DigitalOcean to zeit now since it's using Dockerfiles, but now i'm not sure if I should. Will i just be forced to switch hosting provider in the next year or 2? Truly discouraged about the choice to make literally everything a lambda function
Show more messages