Paulo De Mitri@paulogdm
Show previous messages
clarify future support of docker on now platformNovember 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 more messages
November 9, 2018 at 7:08am
November 9, 2018 at 7:08am
This is frustrating to hear. I have spent so much time trying to get my projects running on Zeit. There are still some issues left, but now all that work seems wasted. Will there ever be possible to deploy stuff like Craft CMS on Zeit? Or will this purely be for custom apps where you can control everything?
Uh... my first thought when I read "Now 2.0" was: "I really hope they do not drive it against a concrete wall...". After reading into it I'm in fear that this might really happen for me. "cloudified Docker" support was one of the key points for me. I've even used Now in examples of several of my print articles to easily deploy some Docker-ized stuff. I planned to convert some JAMstack projects over to Now... but without Docker I do not see how I could run this Rust-code. I really hope that this isn't the end of "Now" as we know it.
Here I am exited as a kid to read the new blog post about Now 2.0. Lets see what the awesome guys at Zeit have in store for us.
Wait... what?! What just happened? Did I miss something?
I honestly thought this would be the announcement of Serverless Docker coming out of beta with the full feature set. Maybe some new features announcements and migration guides for older docker images and node applications.
Boy, was I not expecting this.
Only in august, just 3 months ago, you guys announced Serverless Docker. I was like f*ck yeah this is awesome. Simple docker files for everything. Sub 500ms container startup. Max concurrent requests. Optimised docker images. Running tests as part of your build process. Static deployments using a Docker file. No vendor lock-in. I remember thinking to myself: Dude, this is what the future looks like. And now we are going back to lambdas all over again.
I just think its strange that a flagship feature announced 3 months ago is now just brushed aside. Like "We thought a lot about containers for the past 3 year... and lambdas are superior". Okey, thanks for the update...
You guys probably have your reasoning and I am curious to find out. Maybe its the technical limitations or the feasibility of a business model based on Docker containers. I don't know... from a developer/customer point of view I honestly feel like you guys just took a step backwards.
We literally just yesterday decided that we would switch our docker containers to now.sh after a week of experimenting and testing. Now after this announcement this makes the new service and any future of using it much more dubious. For our infra we already have pretty good serverless lambda support when we need it via the https://serverless.com/ framework.
The timing could not have been worse :/
Unfortunately I couldn't move one of my applications to the serverless paradigm even if I wanted to—I am rendering SVGs server-side and depend on fonts and other binaries to be installed. Docker was the perfect solution and Now's docker hosting was great.
Does anybody in this thread know of any alternatives that provide a similar service to Now v1 docker?
I will be checking out the Docker support at Digital Ocean. https://www.digitalocean.com/products/one-click-apps/docker/
I was refraining myself from asking the question, but have no other response yet from Zeit regarding docker, I think we can share alternatives to other people in this thread..
Thing is I don't even want to have to SSH into a VM
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.
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).