rocky-tools VS AppImageKit

Rocky Linux has migration scripts available at https://github.com/rocky-linux/rocky-tools/tree/main/migrate...

An easy shortcut though, in case you have to hand type it out somewhere, is https://rockylinux.org/migrate2rocky.sh

We have a conversion script for 9 here.

https://docs.rockylinux.org/guides/migrate2rocky/ https://github.com/rocky-linux/rocky-tools/tree/main/migrate2rocky

I used Rocky Linux to migrate the CentOS 8 Servers, the migration was just done using the migrate2rocky.sh script from https://github.com/rocky-linux/rocky-tools/tree/main/migrate2rocky.

You can also convert an Oracle Cloud to Alma or Rocky then install ApisCP. If you do, append -s has_low_memory=1 to the installer.

If going with Oracle Linux it's necessary to convert to Alma or Rocky before installing the 30-day trial. This also doubles as a great hack for a free 1 GB DNS-only server.

I run the migration script today and I encountered this pellicular error:

migrate2rocky.sh is a 1200 line bash script that appears to call dnf dozens of times. Granted, at the time he didn't know exactly what the migration path was going to look like, so call this one a broken promise rather than a false statement.

It's covered in Rocky's docs and the migrate2rocky README, relevant excerpt here:

What you're looking for sounds like AppImages (https://appimage.org/) . I have only used them while downloading games from itch.io, etc. (since i prefer package managers) but they seem to work out of the box on popular distros.

Ideally a new instance of the application is installed for each user. This also provides better isolation if one user upgrades/removes/breaks their application instance. I, for one, have really come around to the AppImage model [0] in the last couple of years.

[0] https://appimage.org/

I found a similar issue on github and tried this solution but still getting the same error .

There is AppImage[1], which packs a lot of stuff into a SquashFS filesystem, appends it to the executable, so everything is in one file.

[1] https://appimage.org

Nah i think yall just hating appimage. Real gold standard.

Although I haven't used plugins feature myself yet, this does sound like the perfect use case for them. Not every patient needs to access every single source. With plugins you can load only the source (or few sources) that they actually need. You can still use something like https://appimage.org/ to give them "a single binary", but will actually contain your slim binary and all the plugins.

```dlopen(): error loading libfuse.so.2 AppImages require FUSE to run. You might still be able to extract the contents of this AppImage if you run it with the --appimage-extract option. See https://github.com/AppImage/AppImageKit/wiki/FUSE for more information```

This doesn't look like a squashfs image. Cannot mount AppImage, please check your FUSE setup. You might still be able to extract the contents of this AppImage  if you run it with the --appimage-extract option.  See https://github.com/AppImage/AppImageKit/wiki/FUSE  for more information open dir error: No such file or directory

appimages. Appimages are similar to flatpaks, exept that they are a file you download and double click to run. Think of them as portable softwares like windows has (portable apps). They are sandboxed too. You can learn more about appimages here