I use GPG keys to sign my commits and work exclusively in devcontainers. In VSCode devcontainers the extension either mounts in or copies in the GPG configuration/keys from the host machine, which allows me to sign my commits. However this does not seem to work in Cursor as my GPG keys are not present within my devcontainer.
Steps to Reproduce
Simply compare the GPG configuration in a devcontainer between VSCode and Cursor.
Expected Behavior
GPG configuration/keys should be mounted or copied into a devcontainer.
Operating System
Linux
Current Cursor Version (Menu → About Cursor → Copy)
While the workaround of specifying a mount of the GPG directory into a devcontainer works, it’s not very portable and requires us to setup additional devcontainer configuration that we don’t have to when using VSCode.
As such, this is quite a painful issue for those of us that bother to sign our commits as we often have to leave Cursor in order to perform a commit. This also feels like it should be a relatively simple issue to solve since the VSCode devcontainer extension is capable of it.
This is a known limitation of our extension. In the meantime, as a workaround, I’d recommend manually mounting the required values / configuring the environment variables in your docker setup.
This is a limitation for me as well. In VS Code, devcontainers are automatically set up in a way that you can use both GPG and SSH keys. Thanks to Cursor, I can’t sign my commits because our company is using devcontainers. This is of course a limitation for many other people as well.
Unfortunately it is not a working solution to modify the devcontainer setup to bind mount GPG directory from the host machine as it would then interfere with anyone working on the repository who is using VS Code instead.
I’m not sure I would agree that this a limitation of the devcontainers extension (in the sense that it cannot do this in the future) as the VSCode devcontainer extension handles this just fine. It also seems like a relatively simple problem to fix as the devcontainer extension just needs to copy or mount in the GPG configuration from the host machine.
I agree with @suojalasit_kirstu in that adding in a mount configuration to the devcontainer configuration isn’t a working solution as it isn’t portable across an organization.
I’d take a crack at creating a PR to fix the issue myself, but I’m not sure if the source for the devcontainer extension is public.
Is it possible to get this on the roadmap? It’s currently my main pain point with Cursor as I need to pop out of it in order to perform a commit.
This problem has been going on for about 5 months now. We even talked about it here before. I literally switched from Cursor to VSCode just because of this — there’s hardly a more ridiculous case than not being able to commit with GPG.
The fact that this issue hasn’t been resolved in 6 months is honestly a comedy.
I’m now using VSCode with Copilot / Claude Code, and I can happily commit without any issues.
