What stood out to me more than this particular project is the visible acceleration of a phenomenon many of us could foresee, especially over the last year or so: people can build a version of the same idea faster than ever.
After like 10 minutes of searching I found multiple similar swift projects (most of them are just a couple of weeks or months old):
There were more if you include ones with fewer GitHub stars, CLI-only, non-Swift etc. but you get the idea.
People will increasingly be able to build their own version of the software they want. As that happens the value of someone else's decreases. The era of hyper-personal software is coming.
My current power move in the age of AI: do nothing.
I had an idea like this and thought I could vibe code it, but then I figured someone else would care more and do it first. I was right!
This looks like a great app and I'm excited to try it out.
Free idea: I would like to be able to "jail" an agent inside a VM and send instructions to the harness from outside the VM to agent(s) installed inside. Ideally there is no Codex/Claude/etc. installed on the host.
More awesome: let me provision multiple user accounts inside the VM and restrict filesystem / network policy by user. Then I can have a dev agent, QA agent, etc. each with its own view of the work. That would be a powerful base layer for further automation.
Of course I should be able to provision various resources "attached" to the VM that agents can use on a permissioned basis; e.g., DB, queue, external volume, and so forth.
> Free idea: I would like to be able to "jail" an agent inside a VM and send instructions to the harness from outside the VM to agent(s) installed inside. Ideally there is no Codex/Claude/etc. installed on the host.
I threw something like this together w a simple browser front end, mostly because I like running mid to large open models but can’t trust them to not go insane. Will share at some point soon
I have been thinking about this too. Is it not as simple as installing Claude in the VM and connecting via an SSH terminal, or if you want a GUI use VSCode with the Remote SSH extension, which will give you the file browser UI etc. Presumably you can extensions in the VSCode Claude/whatever chat extensions in the VM too.
This looks like a really solid app. I like that it's 17 MB and uses the ContainerAPIClient library directly.
28 commits in 3 days, 5,015 lines of Swift, every commit "Co-Authored-By: Claude Fable 5".
Also neat that it's signed/notarized. I installed it and it downloaded the necessary container platform stuff on first launch.
Suggestion: add a getting started tutorial to the site which suggests an image to try out and has screenshots (or a silent video) showing you how to get that image up and running and what you can do with it.
The create image dialog suggests "nginx:latest" but that's not a great starting demo.
Coding yes, copywriting, design, identity, no. Using AI doesn't mean giving up on quality, unless you don't care about quality. Most of these issues come from folks who don't really care about quality and ship the first slop that comes out.
I think the issue is that the prose on the homepage gives off AI marketing BS "Everything you'd expect. Nothing you don't." "Native down to the pixels" etc. in an age where the web is stuffed full of low value llm generated content this is a strong negative signal for me (and i suspect others). No reflection on the app itself which I've yet to try but seems like a great idea
It would be nice if everyone prioritised, and was capable of, shipping polished products. But more likely the apps you're bemoaning come from folks who are not product designers. Even prior to genAI there were plenty of developers (myself included) who had patchy competence in some subset of {copywriting, documentation information architecture, visual design, identity, UI/UX, ...}. I know good developers for whom UI coherence is "not their problem," although they know well enough that it needs to be someone's problem. "Programmer art" is also a thing. I would argue that the non-coding parts of many open-source projects are what lets them down, and when it is good it is usually documentation that impresses me the most. But I think Ze Frank's view might be that, given the sudden drop in barriers to entry, it is amazing that everyone is having a go and trying to express themselves.
A tutorial with a slightly more realistic example would help a lot here. nginx:latest shows the plumbing works, but it doesn’t really show where Apple Containers feels different from Docker Desktop or OrbStack.
Something like a tiny app with a volume, port mapping, and a simple rebuild loop would make the value much easier to see.
Nice, I like the functionality and that it is a tiny native SwiftUI app. I recently wrote a blog [1] on using Apple containers for agentic coding; I just updated it to mention Davit. I so much prefer using Apple containers to using Docker on my two home Macs for personal projects.
How does this compare to OrbStack? Do Apple Containers offer anything in the dev experience that I would notice? OrbStack’s implementation already feels lightning fast for my usage.
Really nice. Worked perfectly downloading the runtime and running nginx:latest.
It's getting to the point that scrolling down on Github and seeing Claude as a contributor is a signal the app will be good (Native feeling, no Electron, etc)
Yeah. I don't quite understand this. Can I use this instead of docker desktop, to run docker containers on my mac 'natively' ? Or this is completely separate from docker ?
This is focused on builds, so running either buildkitd or dockerd in an Apple containerization container.
No port forwarding or host volume stuff (really its focused on running buildkit on mac) BUT complete integration with docker CLI and buildx.
Unrelated. I noticed that the settings window (Cmd-,) text inputs all type from the right instead of the left like older macOS inputs (or web inputs[0])
Is that a thing macOS is moving to? I'm sure I've seen Apple use these too.
Kinda interestingly: it zips to 17MB, but the binary looks to be 56MB (davit.app/contents/macos/davit). That seems like a surprising amount of compression for a binary - embedded assets maybe? Possibly this is normal for mac apps though?
A lot of Mac apps compress like this. Not so long ago, it was pretty common to download a 3-400mb dmg file that decompresses to a 1.5gb app package, for example.
A lot of the time that happened, when I checked it was because a lot of the assets were relatively uncompressed, so DMG-compression shrank them considerably. I haven't noticed the binaries themselves being this compressible.
But that's just "noticed", I definitely haven't paid much attention. And don't have a mac nowadays, so I can't go check my hard drive now.
I'd lean the same way as you (just a hypothesis from me too). A .app on MacOS is just a special kind of directory, so the compression covers the normal file types inside of it.
Localization files compress well, compiled code compresses well, repeating assets (@1x, 2x, 3x) and the pair of binaries in a universal app (x86_64 + arm64) do too, etc.
Ah, and dmg compression is just LZFSE, zlib or bzip2, so pretty standard stuff as far as I understand it.
Hmm… how does one even pick between multiple vibe coded options?
I like to vet my options before committing to new software but who knows if the authors are gonna support these in a month? I don’t want to waste Fable tokens to fix bugs myself when they crop up.
With nothing running, the platform's background services idle at roughly 25 MB. Docker desktop starts a single VM to host all containers and will reserve memory to do so. Davit itself is about 25mb and then each container will use the memory up to what you allocate for it.
Docker desktop on mac does not work well (uses lots of resources) and my current alternative is OrbStack (very slick, uses far less resources, but freemium).
It claims to be backed by (and require) apple/containers(1) which "consumes and produces OCI-compatible container images" so if all that is true .... yes!
OrbStack has its own virtualization layer designed to simulate Docker. Containerization has different primitives even though it supports the same OCI images
Docker Desktop/Obstack start a single VM that runs all your containers. This means that you'll have to scale it accordingly. Davit uses Apple Containers that runs a very thin VM for each container you spin up. Depending on your use case it's more, less or equivalently effcient.
I can’t speak about orbstack, but I’ve worked with docker desktop and podman desktop for years on macOS. Those programs start up a virtual machine that consistently eats ram regardless of whether or not you are running containers in it. Apple container looks lighter weight. In the age of ridiculous ram costs, you gotta save resources.
In addition to memory saver that another person replied about, Docker Desktop also has an MCP server functionality and marketplace (almost all free) and huge AI focus. You can hardly compare it to the others at this point.
I was doing the following at the same time on my MBP this week:
* running a bunch of containers + MCP servers for Claude and Codex on Docker Desktop
* heavily using Claude Code with Fable and packer to build cloud marketplace images
* having Codex write some tests and git flows and reviewing the work in vscode
* automating a character in a Wine-based 1st party RPG in the background running at full resolution
* watching anime on Plex in between Claude Code prompts
It's all about your machine. Docker Desktop is not my worry and if you're a Dev you should have a nice laptop with 32-64GB or more, Apple Silicon Max CPU, etc. This goes for Fusion or UTM also if you want to run a Linux Desktop.
I use docker CE with all container/tui interfaces on all of my Linux systems, but Docker Desktop is nice for macOS or Windows. I almost forgot about Docker Desktop's Gordon, and the AI assistant will do things like analyze your Dockerfile or compose.yml. Super handy.
Docker Desktop's memory saver shuts down VM when containers are not running.
Additionally, Docker/Podman/Orbstack start a single VM, where memory is shared between containers.
On the other hand, Apple Containers create a separate VM for each container, which results in higher memory usage due to Linux kernel overhead, as well as the fact that kernel will try to use most of the available memory for file caching.
After like 10 minutes of searching I found multiple similar swift projects (most of them are just a couple of weeks or months old):
https://github.com/tdeverx/contained-app https://github.com/nico81/iContainer https://github.com/wouterdebie/davit https://github.com/Augani/dory https://github.com/tofa84/berth https://github.com/erdaltoprak/ContainerUtility https://github.com/andrew-waters/orchard
There were more if you include ones with fewer GitHub stars, CLI-only, non-Swift etc. but you get the idea.
People will increasingly be able to build their own version of the software they want. As that happens the value of someone else's decreases. The era of hyper-personal software is coming.
reply