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 1:08pm
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
Can we just have a docker builder as part of the new platform? (best of both worlds)
Then Now 2.0 deployment will be composition of docker builds, seems to replace Kubernetes and Swarm, hehe
they’ve unfortunately already stated that they don’t plan to keep docker support (
It may explain why Zeit chose to move away from containers
Even if they are discontinuing Docker, they should find a way to let us host it in a legacy mode... or are there not enough docker users on this platform for them to continue their docker hosting feature?
I get that the new way might be better and more optimised but I have a bunch of Docker images from clients and our previous work that will not be recoded to work with the new Lambda model...
I think they are letting us host Docker it in the legacy mode 🤔
Until they shut it down...
- What do you recommend for all of us in the GraphQL community? You mention that this use case is 'going to be supported', but some clarification of your intents/thoughts would be great! I imagine there are quite a lot of node-based GraphQL servers hosted on Zeit Now v1/Serverless Docker, and as far as I know, GraphQL doesn't play that nicely with the Lambda approach, seeing as the whole idea is to only have one route/endpoint.
Sure, we can host it using now/node, but I'm not sure the cold boot times is all that great in that case.
Show more messages