Cpak – OCI application package format for Linux desktops, servers and devices

40 pointsposted 8 hours ago
by xlmnxp

14 Comments

nine_k

6 hours ago

In short: structurally like Docker (reuses Dockerfiles), but without a daemon, and, unlike Podman or Nix, very lightweight, only two binaries do everything.

Common chunks of data are shared / deduplicated across installed packages, again like Docker or Nix.

The runtime is under LGPL2.

stephenlf

6 hours ago

> Follow a complete course, change real manifests and see what cpak accepts, refuses or changes. Professional paths lead to an exam and a public, verifiable credential.

Holy Claude

novafunc

6 hours ago

He has a bunch of projects. Most notable being:

- Bottles (Wine/Proton runner)

- cpak

- Atoms (container manager)

- VanillaOS (atomic OS with bespoke tooling)

- Sinty OS (another atomic OS with bespoke tooling)

- Sinty DE (desktop environement + apps)

It's fair to say most of them are AI generated nowadays.

RandomGerm4n

4 hours ago

At least Bottles is really good and not just slop

Groxx

14 minutes ago

tbh I've almost never been able to use it, on ~5 very different machines, across like 10 OSes, and dozens of images through several years. it either fails to start a VM immediately with no usable error message, or seems to run but gets stuck on a blank screen or sometimes grub, sometimes also locking up my computer. manual use of lower-level KVM stuff has worked fine on all of them, by comparison, but it's a pain so I keep trying occasionally and have only succeeded once years ago (and the next image I tried did not work, and then the working one stopped working a few days after).

so I've always been kinda confused why it's included so widely.

_russross

5 hours ago

I've been a Debian user since the late 90s, and their packaging system is the main reason. Not the tools and package format, but the culture and strict rules that govern inclusion in the system.

Every time I see a new package system that promises to free creators of the burden of integration and compatibility with the rest of my installed software, it's a hard "no" from me--and there have been a lot of these over the years. The promise is always how easy and carefree it is for packagers, but the things that make Debian harder are the things that make it valuable. Careful integration with the rest of the system with matching dependency versions. Modular, carefully partitioned packages for complex systems that would otherwise be all-or-nothing. Ongoing maintenance and updates. Responsiveness to security updates. Following common rules for configuration, directory placement, init/systemd integration, etc.

cpak looks like yet another system designed to ignore the rest of my system as much as it can and live in its own little world. In other words, designing around the needs and goals of software packagers over the needs of users and long-term system maintenance. Solving the easy problems instead of the hard ones.

nine_k

3 hours ago

> designed to ignore the rest of my system as much as it can and live in its own little world.

Exactly what a small, locked-down system needs. A single-purpose server box. An advanced appliance, like a "smart TV", or media box, or an advanced home automation hub.

juujian

5 hours ago

Yup. Ubuntu promises the best of both worlds, and in my experience the end result is noticeably worse than Debian. You notice when things are deliberate and tested versus cobbled together and made to work.

noir_lord

22 minutes ago

The weird thing is that Ubuntu manages to sit in some unholy local minima.

Debian rock stable, changes slowly and carefully.

Fedora rock stable, changes rapidly and constantly.

Ubuntu is just painful.

Note: this is on the desktop, I just use Debian on the server as the host OS - some habits are hard to break.

ChocolateGod

5 hours ago

How does this handle runtime updates if the source cpak Containerfile doesn't get rebuilt?

Right now on Flatpak, if I target org.freedesktop.Platform, when that gets security updates to libraries, my application will use them without needing to be rebuilt. I assume for cpak because OCI images are layered based on a fixed content commit, it won't get library updates unless rebuilt.

I do think Dockerfiles are a better mechanism than flatpak-builder specs, the ecosystem is huge.

localhoster

4 hours ago

> holy claude

With comments like this, I'm not even gonna bother opening the link

xlmnxp

8 hours ago

cpak is the OCI application package format for Linux desktops, servers and devices.