open-vm-tools VS AppImageKit

Install open-vm tools (this enables a slew of optimizations).

Kudos to Raviu56 on github

I’m trying to try out Guiz in a VM (specifically VMware), and am unable to build open-vm-tools; I’m currently trying to setup a build environment using: guix shell gcc-toolchain glibc libmspack

I can't say why Alpine Linux doesn't have that package. My guess its due to being a security focused distro it omits it because it could be seen as a security issue. If you absolutely want to use Alpine Linux you could try building it from source (https://github.com/vmware/open-vm-tools/) or us the VMware Tools ISO: https://kb.vmware.com/s/article/1018414

I am wondering if someone have news about the updates of the open-vm-tools package for Rocky Linux (v8.6 or 9) I am trying to update them to fix the CVE 2022-31676. They are available on github but need to be compiled manually (nightmare to maintain later in a professional env) and fedore released an rpm package as well.

Avec la backdoor VMware ahah.

So I think you're hitting this issue.

Check the perfromance with open-vm-tools installed. https://github.com/vmware/open-vm-tools

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