toolshed/organising
8
1
Fork 0
Code Issues 104 Pull Requests Releases Activity

The config commons and podman #693

New Issue
Open
opened 2026-04-06 20:11:52 +00:00 by decentral1se · 0 comments
decentral1se commented 2026-04-06 20:11:52 +00:00
Owner
Copy Link

https://docs.coopcloud.tech/abra/design/

I was testing https://github.com/containers/podlet but sadly immediately ran into a configuration parsing issue. I believe our use of template_driver is blasphemous as it's not officially part of the compose spec and another aspect of abandonware swarm (related: https://github.com/docker/compose/issues/13598).

Opening this up to track any parallel efforts and to make it visible. The ideal of the config commons is that others can make use of it without abra. So, we probably need to have some translation layers which work reliably. We still haven't seen this ideal hit reality 🙈

Podman would only support single-node installs but that would be fine for people who only need that.

> https://docs.coopcloud.tech/abra/design/ I was testing https://github.com/containers/podlet but sadly immediately ran into [a configuration parsing issue](https://github.com/containers/podlet/issues/206). I believe our use of `template_driver` is blasphemous as it's not officially part of the compose spec and another aspect of abandonware swarm (related: https://github.com/docker/compose/issues/13598). Opening this up to track any parallel efforts and to make it visible. The ideal of the config commons is that others can make use of it without `abra`. So, we probably need to have some translation layers which work reliably. We still haven't seen this ideal hit reality 🙈 Podman would only support single-node installs but that would be fine for people who only need that.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
abra
Everything to do with abra
awaiting-feedback
Ping/pong on comms
backups
bug
Something is not working
build
Go build related issues
ci/cd
Getting the robots into the mix
community organising
Opening this thing up
contributing
Contributors stuff
coopcloud.tech
Our main website
design
Design thinking required
documentation
Let's write things together
duplicate
This issue or pull request already exists
enhancement
New feature
fedi
Democratic decision making
fedi-infra
finance
Money things
funding
Anything related to grant funding
good first issue
Easy start with development
help wanted
Need some help
installer
Installation related issues
legal
performance
Performance related
proposal
Large change which requires feedback & decisin making
question
More information is needed
security
Securing our shit
test
Unit or integration test suite
wontfix
This won't be fixed
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
3wordchant aadil abra-bot ammaratef45 Apfelwurm carla cas coopcloud cyrnel decentral1se fauno iexos jade jjsfunhouse jmakdah2 joe-irving kawaiipunk knoflook kolaente lambdabundesverband linnealovespie moosemower moritz notplants p4u1 pharaohgraphy renovate-bot ripclap simon sixsmith stevensting trav val yksflip
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: toolshed/organising#693
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?