I write English / Escribo en Español.

Vidya / videojuegos. Internet. Cats / Gatos. Pizza. Nap / Siesta.

This user’s posts under CC-BY-NC-SA license. Ask me if you need a different permission.

  • 2 Posts
  • 318 Comments
Joined 3 years ago
cake
Cake day: July 26th, 2023

help-circle
  • Oh thanks, I know well about it. podman unshare is the reason why those permission issues are not major (eg.: you don’t need to ever sudo to solve the permission issues rootless causes, I think?). But my going to was more focused o borking the output or workflow of using some of the “usual” tools of a Linux console, such as needing to account for the potential existence of a podman environment on the user account (or any given user account, if doing house cleaning under root) if you ever need to rely on the recursive results of things like chmod or find.





  • I can understand the point that Word is needed for producing some borked, glitched, eldritch formatting that 99% of people expect as correct because Office is that much widespread and has trained people to be Wrong on the Internet; and in that case yeah I would still recommend running a(n older version of!) Office just so that you can process (and test) that you are producing what is expected in the exchange.

    It’s curious actually. While LO compatibility has improved, I don’t think anything close to an umbrella “Imitate Word [$VERSION] Glitches” option has ever been added or even considered for LO? How about the other Word imitators? Can eg.: WPS or Calligra replicate Microslop idosyncracies? Because if so, running those would be better than running Office on a remote.


  • It’s pretty great, and I like that the workflow for creating containers is sliiiightly easier than on Docker. I switched from Docker to Podman for most stuff about a year ago and so far there are only two hiccups that I lament:

    • the higher disk consumption due to not being able to share image storage. (I’ve tried with additionalstorages but that seems to only be respected for podman run; podman build and podman compose seem to ignore it and always pull images from the registries)

    • Some annoying isses with fule permissions due to rootless design - running rootless containers will create files under your user storage that you as a user have no permission to transfer or remove for cleanup or security, and severely breaks the output of tools like du or find due to error spammage.



  • If the only thing you need is not even the whole Office suite but just a Word processor (and not even any particular version) and since you’ll be remoting to it for the graphical access, you don’t need to spin up a whole Windows VM for that. You can just spin up something with Wine and install the Word component from Office 2013 on that (I’d say Office 2013 at most; you might be able to get away with Office 2007 but I wouldn’t recommend it).