Viewing profile — rmolina
rmolina
HN member- Joined
- Fri, Jun 21, 2019, 10:41 PM UTC
- HN karma
- 23
- Public activity
- 23 items
- HN profile
- View on Hacker News ↗
About rmolina
No profile information was provided.
Recent public activity
-
comment
Comment #33540065
Appreciate your comment lmarcos! Yes, the above instruction runs on macos too as long as you have docker-desktop installed.
-
comment
Comment #33539799
You are probably referring to Sysbox ( https://github.com/nestybox/sysbox ), which I believe will meet your requirements (systemd, inner containers, security, etc). Btw, Sysbox is …
-
comment
Comment #24114427
Thanks a lot Peter!
-
comment
Comment #24104522
Right, that will work. I fully agree that Sysbox use-cases extend beyond docker-in-docker and k8s-in-docker. These, docker and k8s, were just the first two system 'apps' that we de…
-
comment
Comment #24097126
We are actively working on this one as @ctalledo mentioned. Please ping us offline if want more details.
-
comment
Comment #24096793
Thanks!
-
comment
Comment #24096776
Please see our response to a similar question below. Hope that helps. Thanks. "The main difference is that Sysbox is OCI-based, so it works with Docker/containerd and hopefully K8s…
-
comment
Comment #24096757
Thank you. Please reach out to us through email/slack. Would love to hear more.
-
comment
Comment #24095580
Didn't know that. But it makes sense given that podman already supports it. Btw, i did a quick search but couldn't find anything on this (docker's systemd support in rhel). If you …
-
comment
Comment #24088745
Thanks @sanketdasgupta for reporting the issue and @asadlionpk for the explanation. Nestybox's github account is an organization now.
-
comment
Comment #24088425
Thanks @geofft, you made a lot of great points. I don't think rootless approach is fully aligned with what we're doing right now. True, we both rely on user-namespaces, and we both…
-
comment
Comment #24087471
Interesting. Thanks @jdoss!
-
comment
Comment #24087311
We haven't had enough cycles to look at Podman in details (yet), but my understanding is that Podman and Docker serve similar purposes: they are high-level runtimes. (i'm obviating…
-
comment
Comment #24087056
As @wh33zle mentioned, CI/CD is an obvious use-case. Development environments is another one (pls see the other question i just answered on this topic). But i also see 'production'…
-
comment
Comment #24086924
Absolutely, that's one of Sysbox's main use-cases, we usually refer to it as 'docker sandboxes'. As you mentioned, the idea is to have your entire dev environment within your fully…
-
comment
Comment #24086367
I see. Will look into that right away. Thanks!
-
comment
Comment #24086178
Thanks for the kind words!
-
comment
Comment #24085859
Thanks! We are out of the critical path, meaning we only emulate interactions with procfs / sysfs, and we only intercept mount syscalls at the moment, so we don't see any tangible …
-
comment
Comment #24085728
Yes. Having said that, we have certain limitations at the moment (e.g. we don't run all cni's), but we are not relying on priv containers as i believe is the case for existing K8s-…
-
comment
Comment #24085669
Sorry, not sure i got that. Can you please elaborate?
-
comment
Comment #24085397
Got it, thanks for the explanation. I clearly see the use-case, just need to review cgroup specs (specifically cpuset) to fully understand if what you mention is already supported …
-
comment
Comment #24085093
Thanks! Both of your suggestions sound very interesting. I personally like the idea of creating large network topologies with a very few outer containers: the real mesh would be at…
-
comment
Comment #24084936
Right, systemd uses pid 1, but it does so within the pid-namespace of the container, so each container has its own systemd. Hope it makes sense. Thanks!