Persistent Profiles and GNU Privacy Guard

[j-simmons-phd]

I have enabled Persistent Profiles for my workspaces and have run into an error using them after rebuilding the workspace image. It appears that re-building a workspace image resets /home/kasm-user/.gnupg. This leads to two errors for users who have keys stored in .gnupg.

1. gpg: WARNING: unsafe permissions on homedir '/home/kasm-user/.gnupg' -- corrected by setting permissions on the .gnupg directory to 700
2. Any keys previously stored are not persisted and must be re-added

Can you update the build scripts to set the expected permissions and to ensure stored keys are not lost during a rebuild operation?

Thank you.

[j-simmons-phd]

Note, this is only happening with the focal-nvidia dockerfile.

[j-simmons-phd]

Upon further inspection, this appears to have something to do with creating custom images. I have put in a work around in my custom images, but would still appreciate assistance in tracking down the root cause.

[mmcclaskey]

@j-simmons-phd , focal-nvidia is currently not released and is only on the develop branch. That being said, it is not guaranteed to work fully in a deployment of Workspaces 1.10.0. It is very likely that persistent profiles are broken on that image, I have opened a ticket internally to look into that. That image, and the tip of develop in general, will likely see a lot of change between now and the release of 1.11.0.

[j-simmons-phd]

Copy that. Like I said, I did get a work around set up, so I am good for now. Thank you for opening the internal ticket and investigating the underlying issue. Looking forward to v1.11.0.