Skip to content

[Bug]: Can't stop containers or Kernel after segfault #757

@sitano

Description

@sitano

I have done the following

  • I have searched the existing issues
  • If possible, I've reproduced the issue using the 'main' branch of this project

Steps to reproduce

I don't have them.

Current behavior

I was interactively in the amd64 ubuntu container (probably Rosetta emulation) on M4 MBP:

container CLI version 0.5.0 (build: release, commit: 48230f3)
apiserver is running
application data root: /Users/.../Library/Application Support/com.apple.container/
application install root: /usr/local/
container-apiserver version: container-apiserver version 0.5.0 (build: release, commit: 48230f3)
container-apiserver commit: 48230f380499efecd663fdc6749a2cbaf2f8ed76

After a notebook sleep I have got Segmentation Fault message in the container's console after what it went unresponsive. After that I could not stop the container and neither I could stop the Container System.

Expected behavior

At least I should be able to force-stop the Container System instead of full Reboot.
Would be nice to be able to force-kill hanged containers.

Environment

- OS: Darwin 24.6.0 Darwin Kernel Version 24.6.0: Mon Aug 11 21:16:30 PDT 2025; root:xnu-11417.140.69.701.11~1/RELEASE_ARM64_T8132 arm64
- Xcode: 26.0.0.0.1.1757719676
- Container: container CLI version 0.5.0 (build: release, commit: 48230f3)

Relevant log output

N/A

Tell me where to get them I will grab them next time.

Code of Conduct

  • I agree to follow this project's Code of Conduct

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions