Cobbler VS go-appimage

I'm looking for Windows Deployment Services equivalent for my Linux network. At the momment i'm using Cobbler (https://cobbler.github.io/) but i'm are looking for a software where i could place .iso images and PXE boot for any machine.

Check out this project: https://github.com/cobbler/cobbler

Take a look at Cobbler. I've used it for quite a few years & love it. It supports both preseed & kickstart.

I haven't setup a PXE server in a long time. There are management tools like MaaS, Collins, Cobbler, etc that deal with the provisioning of systems.

For users and enthusiasts of the Cobbler System http://cobbler.github.io/

if you built a Linux Cobbler server you can do this all

In regard on how to distribute things: If you just want an installation server then I would recommend Cobbler. This server is what is used by Uyuni under the hood for auto-installations. But this would be only reasonable if you really want to try to distribute in a broader way. I am aware that both projects are used from a couple of multiple thousands of machines. So you should be able to bend that system to your desire.

In regard to the installation I would recommend you to have a look at github.com/cobbler/cobbler/ because it would also enable bare-metal provisioning in many scenarios.

What about: Cobbler xCAT

Snap and flatpak run a daemon to integrate into your system. Appimage has an optional daemon to give you the same integration https://github.com/probonopd/go-appimage

Handles making it executable, automatic upgrades, no need to move it to your $PATH, and adds the application to your app list.

Only other thing you might want to do is symlink a friendly name for cli

It's possible to make appimages that bundle a libc, although most don't. The go-appimage project contains a static build tool that will bundle the linker and wrap executable invocation in that. The intention seems to be providing support on older systems for programs built with a glibc that is too new, but I'm using it to ship a musl binary that can run on glibc systems.

I look forward to watching the FOSDEM talk this weekend, so perhaps getting ahead of myself. But I'm curious whether you think the move in appimage toward static linking would solve some of the hairy issues you pointed out? For example: https://github.com/AppImage/AppImageKit/issues/1193 and https://github.com/probonopd/go-appimage/

AppImage This seems like a convenient way of keeping Wine isolated from rest of the system. However, the documentation is still in research phase for this: https://github.com/AppImage/AppImageKit/wiki/Bundling-Windows-applications https://github.com/probonopd/go-appimage https://github.com/TheAssassin/AppImageLauncher https://github.com/sudo-give-me-coffee/wine32-deploy

There's an automatic way to make .desktop entries from appimage, I use https://github.com/probonopd/go-appimage/blob/master/src/appimaged/README.md

There are helper programs to help you manage them and integrate them with the system like other package formats.

their is you can use appimaged https://github.com/probonopd/go-appimage

Would be great if most distros (including Ubuntu, Fedora, etc.) would include AppImageLauncher or appimaged by default. Would make it much simpler for most people.