Request: Add teardown function
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- linux, python
- Domain
- cli, operating-systems
Research direction
Start by tracing archinstall's setup paths for LVM, LUKS_ON_LVM, LVM_ON_LUKS, standalone LUKS, and standalone volume groups to identify how /mnt and related resources are created. Add teardown handling for each combination, then verify that an installation can be retried without rebooting the ISO or host.
Written by the indexing model from the issue text.
Description
describe the request
Currently when LVM or LUKS or a combination of them are selected. /mnt is left hanging on the host
Cleaning this up properly would allow for faster iteration (especially when testing new modifications to archinstall). I believe there is just a small dance depending on if its LUKS_ON_LVM LVM_ON_LUKS or just vg or just LUKS.
But since we create this, we should be able to close it properly.
This also relates to #4035 in the way that you'd want to be able to retry installs with new changes quickly without rebooting the ISO/host (git pull changes, retry patch kinda deal).
- Dominant language
- Python
- Stars
- 8.5k
- Forks
- 774
- Avg merge
- 4d 17h
- Merged PRs (30d)
- 30
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
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.
More from archlinux/archinstall
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
archlinux/archinstall#4807 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
archlinux/archinstall#4603 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
archlinux/archinstall#4385 · 2 comments ·
Maintainers usually reply within 2 days
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
archlinux/archinstall#4813 ·
Maintainers usually reply within 2 days
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
archlinux/archinstall#4808 ·
Maintainers usually reply within 2 days
All issues in archlinux/archinstall
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
BasedHardware/omi#20271 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 92/100
openai/openai-cookbook#3153 ·
Maintainers usually reply within 1 day
-
cvss-severity:high devguard l3montree-cybersecurity/devguard/devguard pkg:golang/github.com/l3montree-dev/devguard risk:low state:open
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
l3montree-dev/devguard#3146 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
bug confirmed issue
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
open-webui/open-webui#31849 · 2 comments ·
Maintainers usually reply within 1 day