Feature request: allow volumes to be mounted as read-only via, e.g.:
hyper run --name mycontainer --volume myvolume:/mnt/point/:ro myimageHyper.sh – Effortless Docker Hosting
161–170 of 218 posts
Re: Hyper.sh – Effortless Docker Hosting
#162Earlier quoted context omitted.
If you use GKE (Google Kubernetes as a service), you really don't need to manage Kubernetes either.
Yeah but is still not as managed as I want. You still need to populate a Kubernetes cluster which is 3 node minimum. Instances show up in your instances list and you still have to be careful to pop your instances in different zones/region for availability. In an ideal world I just want to run containers in a region with a LB in front, I don't care on which Kubernetes cluster they are. That the use case hyper.sh seems…
> 3 node minimum
Since when?
Re: Hyper.sh – Effortless Docker Hosting
#163Is there something like this on top of DigitalOcean/AWS instead? I'd rather rely on those providers for the hardware and uptime.
There are a lot of contenders. Cloud Foundry is one of the many, you'll see others (Flynn, Deis, OpenShift, I always miss a zillion) mentioned in this discussion.
I like Cloud Foundry because I work on it. It runs on AWS, Azure, GCP, OpenStack, vSphere, RackHD and others. If someone wrote a BOSH CPI for DigitalOcean it'd run there too without much fuss.
Disclosure: I work for Pivotal, we donate the majority of engineering on Cloud Foundry.
Re: Hyper.sh – Effortless Docker Hosting
#164This is exactly the service I've been looking for: a fast, cheap, and easy docker deployment service for my personal projects. It'll be interesting to see this grow, and more importantly, see how they handle security and privacy.
I was thinking the same, until I realized that half a gig of ram is $5 which is what VULTR and DO charge for a full virtualized system. My personal projects are mostly webapps that require at least a half a gig of ram. What kinds of personal projects are you working on?
Re: Hyper.sh – Effortless Docker Hosting
#165Surprised not to see much comparison to Joyent Triton on here. We evaluated Triton, and while we encountered a depressing number of show-stopping bugs doing really basic things in the first week (like any container that installs `curl` failing due to a utf-8 character in the default ca set), it was pretty cool to use the native docker CLI to provision nodes. Local == remote on Triton. Triton runs on top of SmartOS in…
Security concerns are what keep me on Triton/SmartOS. Not to mention security is much easier to manage, having been built into the subsystem from the origin of the OS.
FWIW scaling an existing Triton instance is nearly immediate, so my practice is to have a couple smaller containers with my running apps that I can scale up rather than having to deploy in order to start scaling. Then depending on the load I can add more instances after that. Different use case than AWS Lambda-style scaling, but works for 99% of the real world cases I've encountered.
I find the CPU is better than AWS instances, but can be a little bursty due to the way SmartOS shares resources between tenants.
Re: Hyper.sh – Effortless Docker Hosting
#166Hey all, founder is here. I'd like to thank you for your votes here. Really appreciate! Also, I just want to share our public roadmap: https://trello.com/b/7fEwaPRd/roadmap . Feel free to comment. It actually helps a lot for us to prioritize. Thanks!
Hey gnepzhao, great work! I had a question on your quota/metering. How can I get in touch?
Sure, join our slack channel https://slack.hyper.sh/, and DM me there @gnepzhao. See you around!
Re: Hyper.sh – Effortless Docker Hosting
#167Congratulations on launching/going public! I remember seeing your hypervisor/container tech a while back, and it's nice to see a service based around it. A couple of thoughts: 1) Your quickstart ends with a command to remove the test container, but leaves other resources, like the pulled image, billed at 10 cents/started GB intact. That's probably going to surprise some people that start to play with your free credit…
10MB/s is closer to 100Mbps not 1Gbps.
Re: Hyper.sh – Effortless Docker Hosting
#168Earlier quoted context omitted.
Yeah I assumed so. I will re-run my test and kill only one node. I assume any of the three nodes can go down?
Flynn developer here. This is correct, a three node cluster can withstand loss of any single host before things start failing. Also, log shipping and Let's Encrypt support are coming soon.
Just tested killing a node and it worked great.
Re: Hyper.sh – Effortless Docker Hosting
#169Are there any plans for autoscaling groups like in K8S?
Re: Hyper.sh – Effortless Docker Hosting
#170Earlier quoted context omitted.
If you use GKE (Google Kubernetes as a service), you really don't need to manage Kubernetes either.
Yeah but is still not as managed as I want. You still need to populate a Kubernetes cluster which is 3 node minimum. Instances show up in your instances list and you still have to be careful to pop your instances in different zones/region for availability. In an ideal world I just want to run containers in a region with a LB in front, I don't care on which Kubernetes cluster they are. That the use case hyper.sh seems…
Once you've got the GKE cluster stood up (two clicks or so), you don't need to care which cluster you are on. The gcloud CLI remembers whatever you set.
It's very hands-off. And if you ever do want to take more direct control, you've still got the option of doing more or all of it on your own.