What happened?
The SSH_AUTH_SOCK variable is not being set for the user configured in the devcontainer.json, resulting in an unauthenticated context.

What did you expect to happen instead?
The SSH_AUTH_SOCK env var should be set inside the container for the user if possible, or fail if not possible.

How can we reproduce the bug? (as minimally and precisely as possible)
Using DevPod, create an environment with just the following line in the Dockerfile:
FROM invent-registry.kde.org/neon/docker-images/plasma:developer
And the provided devcontainer.json with the most common command (devpod up . --debug).

My devcontainer.json:

{
  "name": "KDE App Dev",
  "build": {
    "dockerfile": "Dockerfile"
  },

  "remoteUser": "neon",
  "mounts": [
    "source=${localWorkspaceFolder},target=/workspaces/${localWorkspaceFolderBasename},type=bind,consistency=cached,Z"
  ]
}

Local Environment:

• DevPod Version: v0.6.15
• Operating System: Fedora Kinoite 42
• ARCH of the OS: AMD64

DevPod Provider:

• Local provider: podman

Anything else we need to know?
The agent is being correctly injected, but the variable is not being set when using remoteUser = node. It works as expected if remoteUser = root or ubuntu.
If I check the owner of the listener.sock, it's ubuntu.

It looks like I'm just using the unexpected user... But if that's the case, a message should be presented or the creation should fail/give a warning.