BOINC VS runc

The only way I can foresee a cryptocoin actually holding value is if spending the coin meant spending processing cycles and RAM doing things like this: https://en.wikipedia.org/wiki/List_of_volunteer_computing_projects But in more general sense, less like https://boinc.berkeley.edu/ and more like AWS... It's the only way to have value, actually holding computing power in a distributed network. - Source: Hacker News / about 1 month ago

Or alternatively: Boinc[1], which has a bunch of different projects. [1] https://boinc.berkeley.edu/. - Source: Hacker News / 2 months ago

Made me think of Gridcoin and BOINC https://boinc.berkeley.edu/. - Source: Hacker News / 5 months ago

The BOINC Census is back for another year! BOINC is an open source software and network for volunteer computing. People can use it do donate their CPU/GPU power to various scientific research areas like cancer, drug discovery, mapping the galaxy, and more. Source: 6 months ago

A few years back, I was in a similar situation and found BOINC(https://boinc.berkeley.edu/) to be a great way to contribute. It's a platform that lets you support various scientific research projects by sharing your computational power and bandwidth. However, it's worth noting that BOINC might tends to be more CPU/GPU intensive rather than bandwidth-heavy. - Source: Hacker News / 7 months ago

It's interesting that, in light of things like this, you still see large software companies adding support for new components written in non-memory safe languages (e.g. C) As an example Red Hat OpenShift added support for crun(https://github.com/containers/crun), which is written in C as an alternative to runc, which is written in Go( - Source: Hacker News / 8 months ago

Yeah, runtimeClass lets you specify which CRI plugin you want based on what you have available. Here's an example from the containerd documentation - you could have one node that can run containers under standard runc, gvisor, kata containers, or WASM. Without runtimeClass, you'd need either some form of custom solution or four differently configured nodes to run those different runtimes. That's how krustlet did... Source: over 1 year ago

Your Docker Container can only run Linux. That's because Docker takes advantage of runC which uses the Linux kernel. You can't run Windows inside of Docker. But of course you can run Docker on a Windows host machine. If you are running a .NET project, you won't be able to use Docker. On the other hand, if you're running .NET Core then you're in luck! - Source: dev.to / over 1 year ago

This is what Podman, an open-source daemonless and rootless container engine, was developed with in mind. Podman runs using the runC container runtime process, directly on the Linux kernel, and launches containers and pods as child processes. In addition, it was developed for the Docker developer, with most commands and syntax seamlessly mirroring Docker's. Buildah, an image builder, and Skopeo, the image utility... - Source: dev.to / almost 2 years ago

If you are curious about how exactly Docker does this I urge to have a look at the following links on layered file system and the library runc and also this great wikipedia overview of Docker. - Source: dev.to / almost 2 years ago