I’m trying to install the 1password rpm and keep getting the following error:
error: Running %post for 1password: bwrap(/bin/sh): Child process exited with code 1; run `journalctl -t 'rpm-ostree(1password.post)'` for more information
when I look at the journalctl it becomes apparent that 1password is trying to create a ‘local’ folder where there is a ‘local’ folder:
Unless you have an overwhelming desire to pay for software which doesn’t install properly, I’d sack it off for Bitwarden. The inability to create a directory which already exists should not be cause for an installation failure, as you’re aware. I’d not trust my secrets to something with that “out-of-the-box experience”.
Even if it weren’t for that mkdir command, if that means it’s trying to put things under /usr/local, that’s a showstopper anyway as that directory is a symlink to the /var partition in Atomic.
Might want to look at the flatpak hosted on Flathub as an alternative or temporary solution until their official RPM package works on a Fedora atomic variant.
Instances like this are where the shortcomings of atomic distributions are exposed, due to their “non-standardness”.
Sorry, I should have elaborated a bit more on my workaround. It is local install with no updates, which was exactly my point, because updates are broken right now. Local install won’t get updates so the broken upstream package won’t interfere with other rpm-ostree updates, so you are safe until they release the fixed version.
I should have also emphasized that the local install is a temporary workaround, once they release the fixed upstream, you just replace your local install with their upstream.
They seem to have already fixed this in their nightly (edge) repo, so I assume we are close to a proper stable release here and the workaround won’t be needed for too long.
However, there are other known issues with the 1password app: Issues · fedora-sysexts/community · GitHub (here it’s the sysext, but the issues would apply similarly). So you might need other workarounds.