Nice _ I am guessing either previous nightlies worked to add apps, or you did those manually? @Suppenkasper
I’m using ElectricEel-24.10.0-MASTER-20240811-233005
Every app was installed using the iX catalog - only hello-world was done manually
Really? Cool - I didn’t see Portainer in the catalog today. Nice to see it there for the start
You have to add the community train
Ahhh - that’d do it! I didn’t think it was far along! even better!!
As a reminder, you can see what apps are in the catalog at any given moment right here:
BTW: thank you so mutch for the hard work on EE - it’s looking better every update!
Even ZFS expansion is working great
On behalf of the team, thank you! We all appreciate it and hope the BETA release in a couple weeks is even better!
Downloaded the latest nightly (from August 19) and installed the very first app. Nextcloud is up and running and I can log in. Electric Eel.
Also now Dockge.
Not seeing the option to add custom app, but hopefully that will appear soon.
Custom compose YAML feature is slated for RC1 (didn’t quite get it done for BETA1), but in the meantime Dockge/Portainer/CLI can be used for random container deployment.
Glad to hear its working for you though on the nightly image! Beta in a little more than a week and excited to get this into more people’s hands.
Just wanted to say thanks very much for all the efforts on this so far, being only a little familiar with docker/k8s etc (I’m more a azure devops/c# kind of guy) I have managed to get a nice docker compose solution in and working using portainer stacks to give with qbittorrent with openvpn…all in a Hyper-V VM for now
I currently “shopping” for a new NAS solution to replace my aging synology 5 drive gutless wonder…sufficed to say I am very much leaning towards truenas scale when electric eel is released (looked at core, scale dragon, os based with lots of cli, proxmox, omv also)
Thanks again
I’ve been testing Electric Eel for sometime, and now that Dockge is available as an application I was able to make a video on migrating Jailmaker Sandboxes
Just a quick minor backend implementation point for those wondering “where is the ix-applications” dataset for the new apps. We’re actually mounting the dataset to /mnt/.ix-apps
(regardless of what pool you choose for apps). This has a few advantages:
- you always know where it’s supposed to be
- the path is never going to appear in NFS exports / SMB shares or be available for a choice as one. Hence, there is no need to document / add validation for it.
Will this have any relation to the eventual “2025 containers”? As in, the “Linux jails” a user creates will also be nested under /mnt/.ix-apps
?
Tbh, I think if system containers were to act similarly, they should at least have their own dataset. I wouldn’t combine docker apps and system containers into single dataset.
But since Incus isn’t even merged yet to nightly for testing I think it’s just too early to talk about it.
There was actually a PR. It was rejected in favor of an alternative approach. Sorry, don’t have the link.
But Incus is coming.
I think it would be good to have an “ix-containers” or some such dataset, like ix-apps, and I think it would be good to mount it in /mint like apps is.
Incus needs at least one “storage” pool to work
I know. The PR for middleware repo was rejected because if you add package to debian control file it pulls not just required but also every recommended dependency which isn’t always needed.
Tbh, this is something debian should fix and make it possible to choose.
So they moved it to scale build repo where they can choose if they want recommend packages or not.
But in this case I would argue that the recommended packages are actually useful.
It’s honestly too early to determine the exact implementation details for that feature.
ditto.
The only disappointment for me is that I installed FluxCD in the k3s cluster and started installing official helm charts, just like I do at my day-job… it was fun while it lasted, learned a lot.
@vampirebyte If you were installing your own Helm charts, you may consider setting up k3s in a sandbox and move your apps there.