[Bug]: container hangs and cant terminate (^Cfailed to send signal: ["error": invalidArgument: "missing signal in xpc message", "signal": 2])
- 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
- [ ] If possible, I've reproduced the issue using the 'main' branch of this project
### Steps to reproduce
```
container run -t nixos/nix
bash-5.3# ls
^Cfailed to send signal: ["error": invalidArgument: "missing signal in xpc message", "signal": 2]
^Cfailed to send signal: ["error": invalidArgument: "missing signal in xpc message", "signal": 2]
^Cfailed to send signal: ["error": invalidArgument: "missing signal in xpc message", "signal": 2]
^Cfailed to send signal: ["error": invalidArgument: "missing signal in xpc message", "signal": 2]
^Cfailed to send signal: ["error": invalidArgument: "missing signal in xpc message", "signal": 2]
^Cfailed to send signal: ["error": invalidArgument: "missing signal in xpc message", "signal": 2]
^Cfailed to send signal: ["error": invalidArgument: "missing signal in xpc message", "signal": 2]
^Cfailed to send signal: ["error": invalidArgument: "missing signal in xpc message", "signal": 2]
```
```
> container run --tty ubuntu:resolute
root@c30d6ce8-2bcf-4e81-ae1b-6009ad4ed69f:/# ls
^Cfailed to send signal: ["error": invalidArgument: "missing signal in xpc message", "signal": 2]
^Cfailed to send signal: ["signal": 2, "error": invalidArgument: "missing signal in xpc message"]
^Cfailed to send signal: ["signal": 2, "error": invalidArgument: "missing signal in xpc message"]
^Cfailed to send signal: ["signal": 2, "error": invalidArgument: "missing signal in xpc message"]
^Cfailed to send signal: ["signal": 2, "error": invalidArgument: "missing signal in xpc message"]
```
### Problem description
Run any container in tty mode. Run any command. It freezes and can not exit anymore.
### Environment
```markdown
- OS: 26.5.1 (25F80)
- Xcode:
- Container: 1.0.0
```
### Code of Conduct
- [x] I agree to follow this project's Code of Conduct
Contributor guide
Research direction
Start by reproducing the hang with `container run -t nixos/nix` or `container run --tty ubuntu:resolute`, then send ^C after running `ls`. Trace the terminal signal path around the reported XPC error, `missing signal in xpc message`. Done means Ctrl-C terminates or returns control from the interactive container without repeated errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos, swift
- Domain
- cli, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100