composefs / composefs/composefs-rs
Suggested layout for sysroot for bootc integration
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 93
- Forks
- 30
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 13
Description
Talking with Allison, when flushed the following potential design for the sysroot layout which would allow us to transition existing ostree based bootc systems to pure composefs ones:
.
├── composefs
│ ├── images
│ ├── objects
│ └── streams
├── ostree
│ ├── repo
│ └── deploy
│ └── fedora
│ ├── deploy
│ │ └── hash.0
│ └── var
└── state
├── deploy
│ ├── composefshash0
│ │ ├── etc
│ │ └── var -> ../../../ostree/deploy/fedora/var
│ └── composefshash1
│ ├── etc
│ └── var -> ../../os/fedora/var
└── os
└── fedora
└── var
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the issue discussion and the proposed sysroot tree, focusing on how composefs, ostree, state, and bootc are expected to transition between layouts. The work is done when the layout design is resolved and the repository has whatever agreed implementation or documentation is required for that transition.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100