Skip to content

Conversation

@copybara-service
Copy link

vfs: Follow symlinks in MkdirAllAt

See #11910 for details — this potentially fixes a divergence between gVisor and
runc behavior where having the cwd of the OCI container spec set to a symlink
to a folder causes gVisor to exit with this error:

running container: starting container: starting root container: starting sandbox: failed to create process working directory "/cwd-folder-name-here": not a directory

Fixes #11910

FUTURE_COPYBARA_INTEGRATE_REVIEW=#11911 from ekzhang:patch-1 3f7bca1

See #11910 for details — this potentially fixes a divergence between
gVisor and runc behavior where having the `cwd` of the OCI container
spec set to a symlink to a folder causes gVisor to exit with this error:

```
running container: starting container: starting root container:
starting sandbox: failed to create process working directory
"/cwd-folder-name-here": not a directory
```
@copybara-service copybara-service bot added the exported Issue was exported automatically label Jul 14, 2025
PiperOrigin-RevId: 783044386
@copybara-service copybara-service bot merged commit b3dff6b into master Jul 14, 2025
@copybara-service copybara-service bot deleted the test/cl783024019 branch July 14, 2025 21:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

exported Issue was exported automatically

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Starting container does not work if cwd is a symlink to another folder

3 participants