[Bug]: start failed NSPOSIXErrorDomain Operation not permitted
- Dominant language
- Swift
- Stars
- 49.9k
- Forks
- 1.8k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 22
Description
### I have done the following
- [x] I have searched the existing issues
- [x] If possible, I've reproduced the issue using the 'main' branch of this project
### Steps to reproduce
I am unable to run any container on my system
container system start
container create --name alpine alpine
container start alpine
container system logs -f
### Current behavior
Unable to start any container
### Expected behavior
Should be able to run a container
### Environment
```markdown
- OS: 26.0.1
- Xcode: N/A
- Container: version 0.5.0 (build: release, commit: 48230f3)
```
### Relevant log output
```shell
2025-10-04 18:18:13.757551-0700 0x142a05 Info 0x0 36144 0 container-runtime-linux: [com.apple.container:RuntimeLinuxHelper] starting start [uuid=alpine]
2025-10-04 18:18:13.763546-0700 0x142a05 Error 0x0 36144 0 container-runtime-linux: [com.apple.container:RuntimeLinuxHelper] start failed [uuid=alpine] [error=Error Domain=NSPOSIXErrorDomain Code=1 "Operation not permitted"]
```
### Code of Conduct
- [x] I agree to follow this project's Code of Conduct
Contributor guide
Research direction
Start by running the reported `container system start`, `container create --name alpine alpine`, and `container start alpine` commands on the stated environment, then inspect `container system logs -f` for the `RuntimeLinuxHelper` permission failure. Done means an Alpine container starts successfully without the `NSPOSIXErrorDomain` Operation not permitted error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos, swift
- Domain
- devops, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100