# Devcontainer Extension does not Mount/Copy GPG Configuration

**URL:** <https://forum.cursor.com/t/devcontainer-extension-does-not-mount-copy-gpg-configuration/146543>\
**Category:** Bug Reports\
**Created:** [December 16, 2025, 7:32pm UTC](https://forum.cursor.com/t/devcontainer-extension-does-not-mount-copy-gpg-configuration/146543 "2025-12-16T19:32:37Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![celestialorb](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/celestialorb/32/38365_2.png) [@celestialorb](https://forum.cursor.com/u/celestialorb)\
**Post date:** [December 16, 2025, 7:32pm UTC](https://forum.cursor.com/t/devcontainer-extension-does-not-mount-copy-gpg-configuration/146543/1 "2025-12-16T19:32:37Z")

</div>

### Where does the bug appear (feature/product)?

Cursor IDE

### Describe the Bug

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)

Version: 2.2.23  
VSCode Version: 1.105.1  
Commit: b3c95a7981bb3057526f1f865e8c307a9911ce00  
Date: 2025-12-15T03:10:57.241Z  
Electron: 37.7.0  
Chromium: 138.0.7204.251  
Node.js: 22.20.0  
V8: 13.8.258.32-electron.0  
OS: Linux x64 6.17.4-76061704-generic

### Additional Information

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.

### Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

---

<div class="post-metadata">

**Author:** ![ravirahman](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/ravirahman/32/20386_2.png) [@ravirahman](https://forum.cursor.com/u/ravirahman)\
**Post date:** [December 17, 2025, 4:08am UTC](https://forum.cursor.com/t/devcontainer-extension-does-not-mount-copy-gpg-configuration/146543/3 "2025-12-17T04:08:05Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![suojalasit\_kirstu](https://avatars.discourse-cdn.com/v4/letter/s/7c8e57/32.png) [@suojalasit\_kirstu](https://forum.cursor.com/u/suojalasit_kirstu)\
**Post date:** [December 19, 2025, 6:39am UTC](https://forum.cursor.com/t/devcontainer-extension-does-not-mount-copy-gpg-configuration/146543/4 "2025-12-19T06:39:29Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![celestialorb](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/celestialorb/32/38365_2.png) [@celestialorb](https://forum.cursor.com/u/celestialorb)\
**Post date:** [December 19, 2025, 7:21pm UTC](https://forum.cursor.com/t/devcontainer-extension-does-not-mount-copy-gpg-configuration/146543/6 "2025-12-19T19:21:06Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![ravirahman](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/ravirahman/32/20386_2.png) [@ravirahman](https://forum.cursor.com/u/ravirahman)\
**Post date:** [January 6, 2026, 11:48pm UTC](https://forum.cursor.com/t/devcontainer-extension-does-not-mount-copy-gpg-configuration/146543/8 "2026-01-06T23:48:07Z")

</div>

This is something that is on our roadmap to add in the next 1-2 months.

---

<div class="post-metadata">

**Author:** ![MuhammetDilmac](https://avatars.discourse-cdn.com/v4/letter/m/c67d28/32.png) [@MuhammetDilmac](https://forum.cursor.com/u/MuhammetDilmac)\
**Post date:** [January 7, 2026, 6:51pm UTC](https://forum.cursor.com/t/devcontainer-extension-does-not-mount-copy-gpg-configuration/146543/9 "2026-01-07T18:51:36Z")

</div>

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.

Thanks, Cursor team! 🚀

> [@Dev Container: git commit fails because GPG can’t be found inside the container](https://forum.cursor.com/t/dev-container-git-commit-fails-because-gpg-can-t-be-found-inside-the-container/120042):
>
> Describe the Bug When I work inside a Dev Container opened with anysphere.remote-containers v1.0.17, every git commit (invoked via Cursor’s Source Control UI) fails: git -c user.useConfigOnly=true commit --quiet --allow-empty-message --file - fatal: cannot exec ‘/opt/homebrew/bin/gpg’: No such file or directory error: gpg failed to sign the data: (no gpg output) fatal: failed to write commit object The container inherits my global ~/.gitconfig, which specifies a host-only GPG path (/opt/ho…

---

<div class="post-metadata">

**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\
**Post date:** [January 29, 2026, 6:51pm UTC](https://forum.cursor.com/t/devcontainer-extension-does-not-mount-copy-gpg-configuration/146543/11 "2026-01-29T18:51:43Z")

</div>

Closed on January 29, 2026, 6:51pm UTC

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.

---

<div class="post-metadata">

**Author:** ![tarun](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/tarun/32/93371_2.png) [@tarun](https://forum.cursor.com/u/tarun)\
**Post date:** [January 30, 2026, 6:26am UTC](https://forum.cursor.com/t/devcontainer-extension-does-not-mount-copy-gpg-configuration/146543/12 "2026-01-30T06:26:56Z")

</div>

Hey guys, I am Tarun, I recently joined Cursor.

I want to start of by apologizing, something like this shouldn’t take so long to implement.  
I actually been at for a week, things do get complicated when there are different OS involved and the protocols will be different for unix based vs windows based.

That said, this is now live on our latest remote container extension – `1.0.32`

I am working on getting it on the remote server’s containers – running into some hurdles.  
Will definitely update it here once that’s done.

And I apologize once again, sorry @suojalasit_kirstu @celestialorb !
