# MacOS - devContainers extension - issues

**URL:** <https://forum.cursor.com/t/macos-devcontainers-extension-issues/115802>\
**Category:** Bug Reports\
**Created:** [July 9, 2025, 11:26am UTC](https://forum.cursor.com/t/macos-devcontainers-extension-issues/115802 "2025-07-09T11:26:06Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![SzymonS](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/szymons/32/69615_2.png) [@SzymonS](https://forum.cursor.com/u/SzymonS)\
**Post date:** [July 9, 2025, 11:26am UTC](https://forum.cursor.com/t/macos-devcontainers-extension-issues/115802/1 "2025-07-09T11:26:06Z")

</div>

### Describe the Bug

With the latest Cursor release `1.2.2` user is asked to replace VSCode devContainer extension with the one developed by Anysphere. The new extension has following issues discovered so far:

- Git credentials are not automatically mounted. Workaround: mounting `${HOME}/.gitconfig` explicitly.
- Sharing docker credentials with dev container is not working at all. I was not able to find any workaround so far.
- Dev container runs as root user by default, for compatibility with VSCode is necessary to set `remoteUser` in `devcontainer.json` explicitly.
- `forwardPorts` from `devcontainer.json` are not exposed in IDE by default. Manual forwarding is required.
- VSCode devContainer extension is not available in marketplace, so there is no option to change a decision user made by accepting the prompt.

### Steps to Reproduce

N/A

### Operating System

MacOS

### Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.2.2 (Universal)  
VSCode Version: 1.99.3  
Commit: faa03b17cce93e8a80b7d62d57f5eda6bb6ab9f0  
Date: 2025-07-07T06:07:27.002Z  
Electron: 34.5.1  
Chromium: 132.0.6834.210  
Node.js: 20.19.0  
V8: 13.2.152.41-electron.0  
OS: Darwin arm64 24.5.0

### Does this stop you from using Cursor

No - Cursor works, but with this issue

---

<div class="post-metadata">

**Author:** ![SzymonS](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/szymons/32/69615_2.png) [@SzymonS](https://forum.cursor.com/u/SzymonS)\
**Post date:** [July 10, 2025, 7:55am UTC](https://forum.cursor.com/t/macos-devcontainers-extension-issues/115802/3 "2025-07-10T07:55:58Z")

</div>

One more: When docker-compose is used as containers source, closing Cursor does not stop docker dev env.

---

<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:** [July 11, 2025, 1:05am UTC](https://forum.cursor.com/t/macos-devcontainers-extension-issues/115802/5 "2025-07-11T01:05:22Z")

</div>

Hi @SzymonS, thank you for reporting these issues.

> - Git credentials are not automatically mounted. Workaround: mounting `${HOME}/.gitconfig` explicitly.

This is fixed in version 1.0.9 of the Anysphere Remote Containers extension.

> Sharing docker credentials with dev container is not working at all. I was not able to find any workaround so far.

Could you share more why you need the docker credentials inside the container?

> - Dev container runs as root user by default, for compatibility with VSCode is necessary to set `remoteUser` in `devcontainer.json` explicitly.

We use the user specified by the `devcontainer.json` or the docker container, falling back to root if neither is set. I would recommend setting the `remoteUser`.

> VSCode devContainer extension is not available in marketplace, so there is no option to change a decision user made by accepting the prompt.

Unfortunately, the VSCode dev containers extension is no longer available in Cursor.

> - `forwardPorts` from `devcontainer.json` are not exposed in IDE by default. Manual forwarding is required.

> One more: When docker-compose is used as containers source, closing Cursor does not stop docker dev env.

We are looking into these two.

---

<div class="post-metadata">

**Author:** ![SzymonS](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/szymons/32/69615_2.png) [@SzymonS](https://forum.cursor.com/u/SzymonS)\
**Post date:** [July 11, 2025, 6:51am UTC](https://forum.cursor.com/t/macos-devcontainers-extension-issues/115802/6 "2025-07-11T06:51:05Z")

</div>

Hi @ravirahman shared docker credentials in dev containers are useful for `docker-in-docker` related scenario which might be enabled via:

```auto
  "features": {
    "ghcr.io/devcontainers/features/docker-in-docker:2": {}
  },

```

Enabling this feature allow us:

- having many isolated development environments with ability to generate docker images inside devcontainer directly
- running development process backing services with help of docker-compose/k8s cluster inside a devcontainer

---

<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:** [July 13, 2025, 10:30pm UTC](https://forum.cursor.com/t/macos-devcontainers-extension-issues/115802/8 "2025-07-13T22:30:32Z")

</div>

Hi @SzymonS , we just released version 1.0.13 of the Anysphere Remote Containers extension, which respects the `forwardPorts` attribute and stops the containers when closing the editor (if running Docker locally).

Thanks for sharing the additional context on passing through docker credentials; we are looking into supporting this.

---

<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:** [August 4, 2025, 10:31pm UTC](https://forum.cursor.com/t/macos-devcontainers-extension-issues/115802/9 "2025-08-04T22:31:06Z")

</div>

Closed on August 4, 2025, 10:31pm UTC

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