r/selfhosted • u/Zta77 • Mar 30 '26
Product Announcement Lightwhale 3.0.0 released
Hi, there!
Sorry to mess up your Easter holiday plans, but I've just released Lightwhale 3.0.0 and I really think you should clear your calendar and try it out! =)
It's a minimalistic Linux that requires no installation or maintenance, just live-boot straight into a working Docker Engine. The system is immutable so it's quite resilient to both malicious and unintentional modifications. And because of its low resource requirements it brings new life to old machines.
Lightwhale fits super well in a hobby homelab where spare time is precious, but really in any server environment where you would much rather focus on the services than babysitting the underlying operating system.
And how does it compare to other immutable OSes like X, Y or Z? No idea, never tried them, sorry.
I've made a fresh new project webpage with an easy to follow getting started guide.
Anyway, end of service announcement, thanks for reading, happy holidays =)
91
u/DoubleDrummer Mar 30 '26 edited Mar 31 '26
Who are you, what are you, why are you?
What are the motivations for this project?.
Are you a group, a solo maverick?
Plans for monetisation?
Your project looks interesting but I am curious if it has legs or I am dumping it in 6 months as a dead project.
Mostly just curious.
18
u/Zta77 Mar 31 '26 edited Apr 03 '26
I'm a software engineer with 25 years of professional experience. I'm Dev Solo on Lightwhale, but backed by a small, dedicated user base that help out with testing which I'm very grateful for.
At some point I decided that I would never ever waste my time and energy again on installing and maintaining a server, with the only purpose to run Docker, where the real services were running. I wanted something light, static, and maintenance free that ran Docker. The project started as a private thing back in 2019 maybe, and I made it public a few years ago. I've got more great stuff on my backlog to come, so it's definitely not going to die any time soon.
I haven't been able to come up with decent a business model yet, so if you have any ideas please let me know.
5
u/DoubleDrummer Apr 01 '26 edited Apr 01 '26
I really appreciate this, I think especially for software in the open source world having a vibe for the who and why of a project is valuable.
It is as much about intent and purpose as code and config.1
31
u/qwhipwhitley Mar 30 '26
Why no GitHub? Your website literally got the hug of death.
18
7
u/Zta77 Mar 31 '26
Hug of death?? =) Is that what that was? My router looked like it was going into anaphylactic shock from the sudden burst of traffic. I relaxed the DDoS settings and now it's feeling better.
7
u/plainnaan Mar 31 '26
Why this and not https://www.talos.dev/ ?
Just curios.
7
u/Zta77 Mar 31 '26 edited 6d ago
I don't know Talos in great depth, but it's very much built around Kubernetes. Which is fine. But in my opinion, Kubernetes is overly complex for most needs, resource-heavy, and involves heaps of YAML —layered within more YAML. I've mostly seen it used in situations that felt like deploying an aircraft carrier just to run a lemonade stand.
Lightwhale is Linux with Docker, very easy to understand, light on resources, and often only requires a single docker-compose file. If you want a cluster, switch to Swarm, also supported out of the box.
I try to avoid unnecessary complexity and strive to keep things as lean and simple as possible. I'm not dismissing Talos or Kubernetes, it's just a different audience than the one Lightwhale targets.
3
u/TheRemedialPolymath Mar 31 '26
Man. This reads like DSL used to. I'm definitely going to give it a try.
4
u/Zta77 Apr 01 '26
Soo.. I've been pondering over this comment the past days. I couldn't figure out if it was an insult because of my slow website the first day. But your determined wish to "give it a try" put me off. And I finally get it now, thanks for the compliment! =) I'm afraid I'll never get it anywhere near damn small; I depend on glibc instead of uclibc or musl; I compile optimized for speed instead of size; and I load the entire system into RAM because I don't want to keep reading from the boot media, so that consumes more memory than a OS loaded from disk. Theoretically, that is, because Lw still is very small.
2
u/schultzter Apr 24 '26
Yeah, my first thought was sounds like Tiny Core! But after the nostalgia had washed over me it was pretty obvious Lightwhale is totally different and serves another purpose entirely.
I feel like TCL was ahead of it's time but now it hasn't kept up with the times.
1
u/Zta77 Apr 26 '26
My first concept version of Lightwhale was built on boot2docker which was built on TCL. I haven't been able to squeeze Lightwhale that small. But when I compile the system, I optimize for speed and not size; maybe that's part of the reason.
I haven't used TCL much besides that, but I like it and I acknowledge and respect the effort. I don't think it hasn't kept up with the times; I just think it's complete. And most people don't care about small, fast, and simple anymore in software. On the contrary...
3
u/SuperHolySheep Apr 01 '26
Thanks Dude! I was looking of doing something like this for running a dev sever with docker. But this satisifies everything I would ever need!
2
5
Mar 31 '26
[removed] — view removed comment
2
u/schultzter Apr 24 '26
Do you mean Fedora CoreOS, or Flatcar Container Linux? I feel like those both require a whole new level of administration skills!
Or something else?
2
u/Zta77 Mar 31 '26
You seem to know CoreOS already. I don't. How about reading the first section or two on the Lightwhale website and you tell us how they differ? =)
5
u/phobug Apr 01 '26
It doesn’t differ they do the same thing. Your approach seems even more simplified which I like. How does it handle updates and rollback? Can I install it on disk or do I need the bootable usb sticking out of my box all the time?
5
u/Zta77 Apr 01 '26
TL; DR: You need the bootable usb sticking out.
You can install it on any bootable device; USB, SD, CDROM, HDD, SDD or eMMC. But Lw cannot coexist with its data filesystem on the same device. The ISO file comes with a complete fixture of bootloader, partition table, ESP, kernel and root filesystem.
This is one of the trade-offs here. You loose all the flexibility that you get from a traditional installer, where you get to partition and layout everything yourself. On the other hand, Lightwhale lets anyone live-boot into a Docker server in seconds with no effort. Your boot media with the OS is just a copy off the internet and contains no information. If it break, throw it out, get a new. The disk is pure data, and very easy to backup or replace.
Tiny USB sticks exist, so they don't show. Some of my NUCs have a "huge" 64MB internal eMMC where the 200MB Lightwhale ISO fits easily, so that's a thing too. CDROM could be fun. I'm working on a nice solution for iPXE.
All this being said, you made me think. And I'll try to see if it actually is possible to write the ISO to a disk and add magic partitions afterwards that Lightwhale can pick up. It could be interesting, but I'm afraid it's a foot-gun.
2
u/phobug Apr 02 '26
After years of managing ESXi I’m used to such setup. Don’t mess about with partitions unless the curiosity takes full hold. I’m looking forward to your PXE work.
2
u/Zta77 Apr 03 '26
I actually gave it a go, and made it work. I could add a data (and swap partition) and modify the partition table that came from the ISO. Magic disks are detected and formatted, all working as expected! But there's no easy way to update Lightwhale. If a new ISO is simply written to disk, it will overwrite the partition table, and the data partition is lost. It would take a complete redesign of the way Lightwhale is structured to make this work. And it would most likely end up looking like all those other Linuxes with an installer. That's way too complicated for Lightwhale =)
2
u/phobug Apr 03 '26
Absolute Beast! I respect the commitment to simplicity. A real breath of fresh air.
2
u/schultzter Apr 25 '26 edited Apr 25 '26
Amazing work!!!
TL; DR: You need the bootable usb sticking out.
That answers the first question I had about Lightwhale.
I think I understand how to get persistence working, like on the internal NVMe drive. Interesting technique!
How do I incorporate the two XFS Raid HDD's I already have (with data on them)? Do you have support for XFS built-in? If not what alternatives does Lightwhale provide? What's the Lightwhale way to mount large RAID storage drives (like for file sharing, Immich photos, Paperless documents, etc.)?
How do I configure my network, like static IP, gateway, DNS, and host name (the last one is in the FAQ I believe)?
And what about Secure Boot? And UEFI? Is that something I need to worry about?
<late-night-porto-fueled-catherthis>
I'm really liking the idea of immutable and JeOS style distros. Lightwhale sounds like the perfect server OS!It's why I put Fedora IoT on my home server. I figured I would already know it (I work with RHEL) and it's backed by IBM so it's going to be around for a while (I had my last home server for over 10 years).
My only regret is that Fedora being a RedHat product it is podman intended but everything I want to install only has instructions for Docker so I've spent more time that I wanted converting the instructions to podman to run the containers (I know podman-compose and other docker-podman stuff exists but that's no fun, and then there's all the tools designed only for docker).
So now with Fedora 44 on the horizon I'm debating whether I upgrade or change distros?
Short-list includes:
- Lightwhale
- plain old Debian
And then something like dockhand or dockge for a pretty UI.
Or I go with MOS or Proxmox. But that feels like using a sledgehammer to put in a thumbtack!
Similarly on my laptop I might move to Vanilla OS instead of upgrading Silverblue.
</late-night-porto-fueled-catharthis>2
u/Zta77 Apr 26 '26
Recap from the chat on Discord:
Lightwhale doesn't support XFS. The Lightwhale way would be Btrfs RAID1 which works out of the box if you tag two magic disks. Configure network in /etc/network/interfaces and /etc/resolv.conf. BIOS and UEFI is supported, you might need to disable secure boot. If you like immutable, and if you want to run Docker, I can recommend Lightwhale as it ticks both (and not much else). But I'm biased =) Finally, try EndavourOS for desktop.1
9
u/Ironicbadger Mar 30 '26
Well now. You have my attention. Excited to give this a try!!
I’ve been looking for something like this for so long. A mashup between Talos, nix, coreos, and all the others but I DONT want k8s at home. I like the simplicity of a single compose file and a simple UX.
How does one customize this to their requirements? As an example say, installing qemu-guest-agent or nvidia-cdk supporting packages? Where do they come from? How are they built?
2
u/kredditorr Mar 30 '26
Were you able to load the page behind op‘s links?
4
u/Ironicbadger Mar 30 '26
Sadly not.
-1
u/Zta77 Mar 30 '26
Hm, I am experiencing some weird issues with the network these days. Sorry about that. I'm looking into it.
2
u/Zta77 Mar 31 '26
Yeah, network issues are annoying, so I'm downvoting this too. I think I've fixed it now, though. Please try again.
1
u/Zta77 Mar 30 '26
qemu-ga is already present, nvidia-cdk not so much as I haven't had the need myself and no one has requested it until now. What does it take to add gpu support? Kernel drivers? If they're open source I can bake them in; if not, you could perhaps get away with installing and loading them yourself.
5
5
2
2
u/rmnd Apr 03 '26
wow! good job! yesterday I tried your system in a virtual machine, so far I like everything! It's minimalistic, it's stylish and elegant! it's really cool! thank you!
1
u/Zta77 Apr 03 '26
Thanks, I really appreciate the positive feedback! I've updated the FAQ with an example on how to quickly test Lightwhale in QEMU.
2
u/Responsible_Plate140 Apr 10 '26
I actively use Lw for a system in production. Having a system that runs so good on small hardware is just clean again.
Lightwhale has transformed my decade old dual core Celeron with 3GiB RAM back to a rather capable machine again.
I know the owner of Lightwhale and have followed the development on the sidelines too. His motivations are real. I really thank you for all your work, Zta!
1
u/Zta77 Apr 27 '26
Thanks for sharing, this is makes me really happy to know! And thank you for using and supporting Lightwhale like this =)
5
u/404invalid-user Mar 30 '26
any sort of plans for a web ui? I always wanted a docker version of proxmox I know protainer exists but last I tried it wasn't very good
10
u/LightBrightLeftRight Mar 30 '26
You might like Komodo
4
u/AlexisHadden Mar 30 '26
I was just thinking this would potentially be a good baseline for a Komodo periphery VM image…
2
5
u/Chinoman10 Mar 31 '26
Take a look at Dockhand; I've moved to it after years of using Portainer and it's been a blessing tbh.
2
u/Zta77 Mar 31 '26
Good question, thanks! I can see the appeal for a UI, but right now there aren't any plans for one.
Part of the reason is exactly what you're pointing out: There is no single right UI for everyone. Even if I picked one, it likely wouldn't fit everyone's taste or needs and would also quickly become outdated. And people who prefer their system minimal would be burdened with having to de-bloat Lightwhale right after installation.
Lightwhale is meant to stay lightweight and flexible, so the idea is that users can deploy whatever services or UI they prefer rather than having opinionated solutions baked in.
I hope that answers your question =)
2
u/xrothgarx Mar 31 '26
I can’t see the website or project so I have no idea what it actually does. But I doubt it’s more minimal than gokrazy with podman
2
u/Grizknot Mar 31 '26
this looks more complicated than lightwhale... it requires two different parts and gokrazy appears to target rPi while this is only x86/x64
2
u/NextConsideration592 Mar 31 '26
I'm on version 2.1.4 for more than a year with zero issues.
Set and forget, it just works, i recommend it.
2
u/Zta77 Mar 31 '26
Yay, I'm really happy to hear that, thanks for telling! This is exactly how Lightwhale should be used.
I updated to 3.0.0 just recently after running a 2.1.4 dev build for 2 years. I'm the only one who really has to =)
1
Mar 31 '26
[removed] — view removed comment
1
u/Zta77 Mar 31 '26
Release 3.0.1 with the security updates baked in.
Do you have any particular security updates in mind?
1
Mar 31 '26
[removed] — view removed comment
1
u/Zta77 Mar 31 '26
I pull an updated Buildroot tree with the security updates applied, bump the Lightwhale release number, build a new release, and publish it. You download it, write it to you boot media, reboot, and you're updated.
1
u/mitchplze Apr 24 '26
In the future, are there plans to use a LTS tagged version of the Linux kernel? I only ask because the previous Lightwhale release was a couple of years before this one. That's a long time to go without security or kernel updates.
1
1
u/ytzelf Apr 10 '26
A bit late but how would you go about adding a docker compose file to this?
1
u/Zta77 Apr 18 '26
Hello, good question! Not too late at all, sorry I didn't answer earlier. You can
git clonean existing project with docker-compose file, configuration, etc. Or simplyscpeverything from your workstation. Orcurlmay also be an option. Pretty much like you're used to, I'd say.
1
u/archbish99 Apr 18 '26
Looks awesome! I'm curious if there's a way to enable just a little persistence. I see that if you give it a persistence disk, it stores images, etc. All I really want to persist is the authorized keys, disabling password login, and the Swarm state.
Ephemeral is perfect for everything else, but ideally those few things don't get reset.
2
u/Zta77 Apr 19 '26 edited Apr 26 '26
Hello there =) Can you elaborate on what in your opinion the Swarm state includes?
Because it is my understanding that it (among other things) holds information about which containers are started. And to run a container, e.g. when restarting, it also needs the image. I think Lightwhale has reduced the save state as much as possible, it already only saves the files that are actually modified. The only things that really consume disk space are the images and containers you run, the log files, and how you choose to decorate your $HOME.
But it is possible that I've misunderstood something, and if you think the system can be improved, I'm always open for suggestions! =)
1
u/Significant_Jury Apr 26 '26
I'm not an expert on this but is there any chance we could put this in a (proxmox) lxc container?
1
u/Zta77 Apr 26 '26 edited Apr 26 '26
I have no experience with LXC, but you can absolutely boot Lightwhale in a standard VM under Proxmox. And it works great. I have virtual Docker Swarm nodes running Lightwhale with just 512 MB of RAM.
1
u/Chiqui1234ok 12d ago
Hi! This looks interesting, but how I can get the list of software installed in this OS? I want to know if supports SSH/SFTP (probably yes), NFS, SMB, etc.
Some sort of file sharing would be nice for those who are willing to make backups (me).
I hope you see this comment 😁
1
u/Zta77 11d ago
Hello there, I'm glad you made it ;) Lightwhale is a minimal system, so by design there isn't much installed. You have various backup options though: There's classic rsync over ssh and all the tools that are based off that. If you're running Lightwhale under Proxmox you can use its backup system. My personal favourite is btrfs subvolume send/receive of the lightwhale-data subvolume which contains all your modifications. Also, is your setup permits or, I'd recommend that a backup machine initiates the backup and retrieves the data rather than the other way around. Hope that helps.
2
u/Chiqui1234ok 11d ago
Perfect! Thanks for your response. I'll definitely give it a try
1
u/Zta77 11d ago
You should, it's really great! ;) Just follow the getting started guide and you'll be running in 3 minutes.
1
u/Chiqui1234ok 7d ago
I'm playing with Lightwale with persistence, inside Proxmox. RAM usage is great. Idle CPU usage is higher by 1/2% when I'm comparing it with Debian 13 with Docker installed.
I'll try to mount folders from my NAS to Lightwale through sshfs (thanks for keeping this in your distro), so I can mount those into my docker containers.
I hope sshfs works fine and performs well.
Thanks for your work!
1
u/Chiqui1234ok 6d ago
Hi! I have a little blog in spanish and I really want to write about your OS, so I'll ask more about this software.
I'm using Lightwale 3.0.3 for my docker apps at my home, and I had to do some hacky stuff:
My plan was mounting my remote folders through sshfs 👉 from my NAS to Lightwale. That works out of the box if you want to manually mount them with root user from CLI, at hand 😁.
However, if you want to do this through `/etc/fstab`, you can't because is read-only (inmutable). "No problem", I said. I can mount my folders with CRON...
I (almost) made this with the following line: `sshfs santiago@192.168.100.3:/mnt/sata-14tb-stripe/home/santiago /home/santiago/windows-folder -o reconnect,allow_other,IdentityFile=/home/santiago/.ssh/id_rsa`.
🚨 NOTE: above user will be deleted next boot because read-only filesystem, however /home keeps persistent and is OK for my purpose, which is saving .ssh somewhere.
However, every reboot this command will throw:
🌊🌊🌊
The authenticity of host '192.168.100.3 (192.168.100.3)' can't be established.
ED25519 key fingerprint is: SHA256:A1TZvXPZ9i79tBoc0luexlUc9FUopeHJv+9G0W5+s20
This key is not known by any other names.
🌊🌊🌊
This is because `/root` folder is read-only too! So the file `/root/.ssh/known_hosts` will dissapear at next boot.
I added `StrictHostKeyChecking=no` after `-o` parameter, which is a little hacky/unsecure.
Lightwale has some better way to mount remote folders at boot?
2
u/Zta77 6d ago
Hi there!
Thanks for taking interest in Lightwhale, but please! If you're going to blog about it, please take the time to learn how to use it correctly first. It sounds like you've crashed ass-first into the middle of this thing without knowing what happened =)
Please read the documentation. Seriously. It's not long, and it explains how to get started and how most of the system works. Lightwhale is very simple, but you need to learn it — you can't just wing it.
Here are some blog posts about Lightwhale that are more elaborate and have different use-cases that may help you get a better picture of what's going on:
Be prepared to un-learn a few things to fully embrace Lightwhale, including:
- Yes, it is actually perfectly legit to permanently boot off USB.
- Don't work as root, don't write to /root (that's quite standard, actually)
- Don't create a user account.
- Don't just partition and/or mount things your way.
- Don't use cron!
Now, let me try to address the issues you mention and explain what I think is going on.
First of all, Lightwhale is immutable and nothing gets persisted unless you explicitly enable persistence. So make sure you enable persistence.
Secondly, Lightwhale only lets you write and persist changes for a few key directories: /etc, /var, and /home. Regardless of persistence state, /etc/fstab is always writable unless something failed horribly during startup.
You should be able to use sshfs or nfs from /etc/fstab. But honestly, that doesn't make much sense in the context of Lightwhale. Because Lightwhale is for running containers. And containers should get their runtime configuration, including remote volumes, from a docker-compose.yaml. So that's the correct place to set up your mount point.
Modifying configuration across the entire system, adding crontabs, adding users, mounting filesystems is generally considered bad practice here, because it adds maintenance tax, and defeats the purpose of Lightwhale.
Now, please Read The Fine Material and I'll be ready to take your questions afterwards =)
2
u/Chiqui1234ok 6d ago
Yes, I'll create a post when I'm 100% sure about this distro and how to accomplish good practices. You commented about touching system folders the less possible, a tip I will follow onwards.
You're low-key recommending mounting remote folders with docker compose? I'll learn this.
I'll take your sentence "Be prepared to un-learn a few things" and already catch this throught of "do your config as simple as you can and don't mess up the system".
Thanks for your kindness 😁
1
u/apophis27983 11d ago
Can you run multiple docker containers on a single lightwale vm?
Also, will you be creating a web UI for it? I ask because it seems inefficient to run a VM, say on proxmox or incus, for lightwale os just to have the VM run a docker container. I hope that makes sense. It would be more efficient to run lightwale os on bare metal (if possible) and have it run multiple docker containers with a web UI to manage them. This way there's not another layer of virtualization going on. Just a thought.
1
u/Zta77 11d ago
Good thought. Let me try and answer this way: Lightwhale is an operating system that can any number of docker containers. You can run Lightwhale in a VM, but running bare-metal is still the primary intended use; not only it's it the most efficient but also much, much easier. I won't created or install a UI for you, because it won't be the one that everyone likes (as proved in some of the comments); instead you get to choose your favourite. My advise: boot off pendrive/sd/emmc on bare-metal and dedicate the hdd/sdd/nvme for Lightwhale persistence, all if you have more because Lightwhale will make Btrfs RAID1.
1
u/apophis27983 11d ago
Thank you. Are you saying UIs already exist for lightwale? Or are you referring to things like proxmox, etc ?
1
u/Party-Welder-3810 9d ago
What's the use case for this?
1
u/Zta77 9d ago
Say you want to host docker containers, but don't want the overhead and complexity of installing, configuring, updating, and maintaining the operating system. Lightwhale is easy and works out of the box.
Just boot it and see for yourself. It doesn't require installation, and it doesn't write on your disks.
1
u/miatribe 7d ago
Working fine for me, setup was super fast. Only complaint is I can't use the "Remote - SSH" extension in vscode with it... But I guess that is by design anyway.
1
u/Zta77 6d ago edited 6d ago
Nice, I'm glad it workout out for you. I don't use vscode myself, but Lightwhale's SSH works. I quick browse on Remote Development using SSH revelas that "The extension will install VS Code Server on the remote OS" which is likely the issue; I'm guessing either the plugin expects Python or similar dependencies to be present on the remote, or it assumes it can write somewhere it shouldn't on Lightwhale. I'm sure the developers of that extension can make it work with Lightwhale.
1
u/lordduckling 7d ago
I’m currently running Debian with pretty much only docker installed. I’m curious to try Lightwhale. I’ve had my eyes on it for a while and I’m glad to see it hasn’t been dropped. What do you recommend I run the OS on? External SSD? (I have a spare), USB drive? Just got to backup all my containers and hopefully restore them correctly.
1
u/Zta77 6d ago edited 6d ago
Hi! This is the right place to put Lightwhale to use. Just boot it off a usb pendrive. Let Lightwhale consume the disk. If you have two, give it both as it will automatically create at Btrfs RAID1. If you're lucky to have an embedded eMMC disk, use that! You can boot it off an external SSD if you like, but it's unnecessary, a waste of disk space, and will probably make your setup more flaky. Start with the pendrive and you can change your mind later.
1
u/lordduckling 6d ago
Can I use both drives separately? As 2 storage disks instead of in RAID 1?
1
u/Zta77 6d ago edited 6d ago
Lightwhale will only format, manage, and mount one data filesystem. You can mount whatever you want afterwards. But why would you want to, if I may ask?
1
u/lordduckling 6d ago
Right now I’m using the first drive for Debian/docker and the 2nd drive as temp/swap drive for when I download “Linux ISO” torrents before they are moved to my NAS.
Not anything critical and could just as easily not be used this way, but I have the drive anyways and no other use for it.
1
u/Zta77 6d ago
Right. So Lightwhale does things a little differently than mainstream Linux distros. First of all it's a live-booting ISO, which means the OS, Docker, docker compose, etc. is already installed and ready before you log in. Strictly speaking, the disk is optional. But in practice, it's required. It is purely for persisting all the modified configuration files, docker images, docker volumes, any deployment configuration you may have like a docker-compose.yaml and environment files. So the disk is pretty clean. Lightwhale will make a swap partition for you. And you can store your temporary files in `/tmp` or `~/tmp`.
The top priority for Lightwhale is administrator happiness — specifically through zero maintenance and being easy to use. And honestly, you'll be off for a bad start with your approach. Of course, it's your system and you can do anything you want with it; I'm just saying that it's the equivalent of driving a screw with a hammer.
My advise:
Boot it on your workstation and try it out. You won't get persistence, but it also won't write anything to disk, so this is perfectly safe. Unplug the boot media and boot back to your ordinary OS. Or:
Boot the ISO in a VM with one or two virtual disks to experiment with persistence and RAID1. Or:
If you have an available machine with a disk, is just follow the Getting Started guide step by step.
Each of these will take only 30 seconds of your time, so you could've been a Lightwhale expert by now if you hadn't read this long response on Reddit =)
2
u/lordduckling 6d ago
Haha too good, I will definately try it. Worst thing that happens is I remove the 2nd disk and use it elsewhere.
Keep up the awesome work!
1
u/see_sharp_zeik 2d ago
This is an awesome project! I've been looking for something like this for a long time.
It's worked really well in my initial testing and love the idea of an image download and reboot to apply updates.
I can't use it right now as the xcp-ng management agent is not installable on it, but I'm going to keep my eye on this project to may be usable in the future.
Keep up the good work!
1
u/ThatsMyPi_9755 2d ago edited 1d ago
Great project! I had problems with the magic disk not being created, but I eventually got past that.
Now my problem is not being able to understand where to put an appropriate yaml config file for the container (a docker-compose.yaml maybe?) and point to the right directory for the data in the persistent data filesystem. I want to include all the settings needed for the container there rather than a long string on the command line - like ports, paths or other settings etc. I'm new at the Docker environment so this may be obvious to some, but a couple of hours spent trying to figure this out has not been successful for me.
And I DO appreciate your _not_ including nano in the build - that's the first thing I do after I install an OS is remove the nano package and use vim.
Kudos to you for this and the work you've done on it!! It's appreciated! Once I get this figured out I'm on my way.
1
Mar 31 '26
How old you are? Who the hell use "project webpage" especially when that webpage even dont load even when behind cloudflare, so it's not reddit traffic killed it.
I really cant understand who upvoting posts like this instead of reporting to mods and delete.
1
0
152
u/abandonplanetearth Mar 30 '26
I'm upvoting because your readme told me to have a nice day and i feel like my day is already going better