-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Version 1.0 changes #51
Comments
I still use Darch as my main workstation having moved from NixOS and I never been more pleased. I like the idea to use Docker instead for recipes, it opens the world to a lot more supported images. Porting recipes to Docker should be trivial, I see that easily possible with mine. I don't know about persisted boots, I'm not really into that kind of stuff, I just mount /home to a image so that my documents are persisted. |
Thanks for the kind words!
You won't be impacted by that feature. The only change you'll see is the move to Dockerfiles for building. |
I wasn't thinking it would be, just sharing how I managed persistence. In any case, I can't wait for Dockerfiles to be implemented! I was thinking of this too, especially when Ubuntu 20.04 came out, which I would understand could now be done with a Docker base image, right? |
The base images were always provided via docker. Also, there is a new base images for Ubuntu 20. I started upgrading, but I'm waiting for some other packages to get official support. |
I'm a current NixOS user strongly considering trying Darch! I have a few questions that I couldn't seem to find the answers for, it'd be lovely if you could help--
Thanks so much for the cool work on darch; it seems really cool and I'm excited to try it! |
I'm a little late to the party here. I've been using darch since January on three different computers all inheriting from a common base set of recipes. I love it! I'd love the ability to do a bit of grub menu customization. I saw someone in the issues a while ago who moved the darch hook to |
Hey guys, I know there hasn't been a lot of activity here. I consider this project to be "done".
BUT, improvements can be made.
First, I want to change the scope of this project. Currently, Darch is responsible for building and integrating with your local GRUB install. I'd like to change that to only be responsible for the GRUB portion.
darch recipes build
- They were great, but there were many nice-to-haves needed to bring it on par with what you'd expect from traditionaldocker build -f Dockerfile
builds. I switched my personal recipes fromdarch recipes build
todocker build
(here) and it worked out great! Let's remove that concern from Darch.apt
-derived solutions officially-supported (Ubuntu/Debian), moving Void/Arch to community-supported - Arch is currently working great, but there is an outstanding bug in Void that I don't have the bandwidth to address. Since I'm not personally using either Arch or Void, I'd like to rely on the community a little here. The only thing that really has to be managed is the initramfs scripts.docker
orcontainerd
for image storage. Instead of treatingdarch
as the storage mechanism for images, I'd like to make it rely oncontainerd
(current) ordocker
instead. That meansdarch stage upload <image-name>
would have something like a--docker
or a--containerd
flag. In each approach, the workflow would be:a. Check local (docker|containerd) for .
b. If it doesn't exist, pull the image.
c. Extract image for squashfs/rootfs integration into GRUB.
This will allow for a seamless
docker build . -t my-image && darch stage upload my-image
.Thoughts? I'm not sure when I'll get to this, but these are the last remaining buttons before I really call this project complete.
The text was updated successfully, but these errors were encountered: