[Bug]: macOS 26.2, container 0.6.0; containers are always removed when they stop even though '--rm' was not specified

[ChrisJ60]

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

Any time I run (or create then start) a container, when it stops it disappears and is no longer found (ls -a does not show it, any attempt to reference it in a command says it cannot be found).

I would supply logs but since the container is not found I cannot.

This is especially problematic if the container does not start properly due to soem error, then it gets removed and so you cannot view the logs to find out anything about the error.

Current behavior

See above.

Expected behavior

Unless '--rm' is specified at create or run time, the container should remain after it has stopped.

Environment

- OS: macOS 26.2
- Xcode: 26.2
- Container: 0.6.0

Relevant log output

N/A

Code of Conduct

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

[jglogan]

Can you provide specific reproduction steps for this?

Also, does this reproduce under 0.7.1?

[ChrisJ60]

Can you provide specific reproduction steps for this?

Also, does this reproduce under 0.7.1?

I upgraded to 0.7.1 (what a palaver that was!)

What I see now is that if I successfully create a container, but then the 'start' for that container fails, the container gets removed.

Here is an example:

$ container ls -a
ID  IMAGE  OS  ARCH  STATE  ADDR  CPUS  MEMORY
$ container create --name pihole -v /Users/Shared/Container/pihole/volumes/etc-pihole:/etc/pihole -v /Users/Shared/Container/pihole/volumes/etc-dnsmasq.d:/etc/dnsmasq.d --dns 10.0.200.10 --dns 10.0.200.15 --publish 127.0.0.1:53:53 --publish 127.0.0.1:80:80 --publish 127.0.0.1:443:443 -e 'TZ=Europe/London' -e 'VIRTUAL_HOST=pihole3.home.thejenkinsfamily.org.uk' -e 'PROXY_LOCATION=pihole3.home.thejenkinsfamily.org.uk' -e 'FTLCONF_dns_upstreams=10.0.200.10;10.0.200.15' pihole/pihole:latest pihole
$ container ls -a
ID      IMAGE                           OS     ARCH   STATE    ADDR  CPUS  MEMORY
pihole  docker.io/pihole/pihole:latest  linux  arm64  stopped        4     1024 MB
$ container start pihole
Error: internalError: "failed to bootstrap container" (cause: "internalError: "failed to bootstrap container pihole (cause: "unknown: "bind(descriptor:ptr:bytes:): Permission denied (errno: 13)"")"")
$ container ls -a
ID  IMAGE  OS  ARCH  STATE  ADDR  CPUS  MEMORY
$

[tfalamu]

Similar experience, I just "lost" a container that failed to start:

$ container start -ia test
Error: internalError: "failed to bootstrap container" (cause: "internalError: "failed to bootstrap container test (cause: "invalidState "container expected to be in created state, got: shuttingDown"") "")

$ container start -ia test
Error: notFound: "get failed: container test not found"

[JaewonHur]

Very simple test case:

container create -it --name test -p 10032:10032 debian:bookworm
python3 -m http.server 10032 &
container start test

The container is lost.