Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
scprodigy
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
7 ms
·
31.
▲
by
scprodigy
10y ago
No, it is HyperContainer. https://github.com/hyperhq/hyperd
32.
▲
Hypernetes: Bringing Security and Multi-Tenancy to Kubernetes
(blog.kubernetes.io)
109 points
by
scprodigy
10y ago
|
29 comments
33.
▲
by
scprodigy
10y ago
check github.com/hyperhq/hyperd
34.
▲
Show HN: Hyper_ – Simple and Secure Container Cloud
(blog.hyper.sh)
88 points
by
scprodigy
11y ago
|
48 comments
35.
▲
by
scprodigy
11y ago
No, the problem of VM is not virtualization, but the notion of "machine". What Docker really does is to get rid of the full-blown machine/guest os, and focus on app. As such, you can run Docker image with Linux container for
36.
▲
by
scprodigy
11y ago
In my own VM, or share a VM with others?
37.
▲
by
scprodigy
11y ago
What about execution isolation? Any info?
38.
▲
by
scprodigy
11y ago
Then how different containers get isolated from each other?
39.
▲
by
scprodigy
11y ago
Yes, the point is that decentralization consensus doesn't help.
40.
▲
by
scprodigy
11y ago
Guess the question is why you want a network of nodes, all of which may append a fake record, if you only want no one to change the data.
41.
▲
by
scprodigy
11y ago
Decentralized consensus does not solve data immutability. The append-only feature in Blockchain does that. So, you only need an append-only DB, without any form of decentralization, to do the same job.
42.
▲
by
scprodigy
11y ago
Have you checked with hyper.sh?
43.
▲
by
scprodigy
11y ago
The difference is not nesting your container in VM. Instead, the container is secure, isolated as VM. Then container becomes the foundation for hosting platform, e.g. EC2, not just app deployment atop IaaS.
44.
▲
by
scprodigy
11y ago
The multenancy challenge comes from the lack of isolation in container. Therefore, people nest containers in VM and put a scheduler atop. But if there is secured, isolated container, we won't need the VM nor the scheduler, the containe
45.
▲
by
scprodigy
11y ago
Right, guess what I'm proposing is more of VPS and Iaas, not containers nested in VM.
46.
▲
by
scprodigy
11y ago
Not really, what I'm saying is more like DO, atop of secured container. Also, it is more of a VPS or IaaS, not have to be CaaS or Microservices.
47.
▲
Ask HN: Will you use (pay) a Dockerized hosting service?
6 points
by
scprodigy
11y ago
|
10 comments
48.
▲
by
scprodigy
11y ago
Try Hyper on Mac: https://hyper.sh/blog/post/2015/07/30/running-containers-fro...
49.
▲
by
scprodigy
11y ago
Check this: https://news.ycombinator.com/item?id=10045714
50.
▲
by
scprodigy
11y ago
Well, Docker still doesn't support all linux distros, so it doesn't run anywhere.
51.
▲
by
scprodigy
11y ago
Why not?
52.
▲
Running containers from Mac OS X
(hyper.sh)
14 points
by
scprodigy
11y ago
|
3 comments
53.
▲
by
scprodigy
11y ago
So, for each Docker image, hyper creates a VM?
54.
▲
by
scprodigy
11y ago
I'm not sure I understand this. How is it different from b2d?
55.
▲
by
scprodigy
11y ago
Yes, but there is no guest OS anymore. No more configuration in the VM instance.
56.
▲
by
scprodigy
11y ago
Photon is built for this case: a minimalist OS to run only as guest. However, check out hyper.sh, the project uses hypervisors to run Docker images, which completely eliminates the need of guest OS, making the whole stack immutable while ju
57.
▲
by
scprodigy
11y ago
People use Docker in a public cloud (VM), primarily to simplify the deployment pipeline, not for LXC. Given this, it actually makes sense to combine VM with Docker, check out www.hyper.sh
58.
▲
by
scprodigy
11y ago
Hmm, I happen to know some details of that. It is actually a quite powerful technology with some out-of-box ideas.
59.
▲
Show HN: Infastructure Policy as a Service (cloudfielder.com)
2 points
by
scprodigy
12y ago
|
0 comments
60.
▲
Ask HN: Does it make sense to make Hypervisor more like Container?
2 points
by
scprodigy
12y ago
|
1 comments
More ›