SO not lauching after turn off via system #193

New Issue

2025-12-29T05:24:24+01:00

adam commented

2025-12-29 05:24:24 +01:00

Originally created by @Enzodtz on GitHub (May 26, 2021).

My container was running fine until I turned it off by the mac's inside button. Now, when I start it, it automatically exits with code 1.

$ docker start wonderful_edison
wonderful_edison

$ docker ps -a
CONTAINER ID   IMAGE                          COMMAND                  CREATED       STATUS                      PORTS     NAMES
1a9cd189f31c   sickcodes/docker-osx:big-sur   "/bin/bash -c 'sudo …"   9 hours ago   Exited (1) 36 seconds ago             wonderful_edison

I'm not pretty sure if that's exact the problem, but that was probably the only abnormal thing I did the last time I ran it.

Is there anything I can do to recover it?

Thanks

Originally created by @Enzodtz on GitHub (May 26, 2021). My container was running fine until I turned it off by the mac's inside button. Now, when I start it, it automatically exits with code 1. ``` $ docker start wonderful_edison wonderful_edison ``` ``` $ docker ps -a CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 1a9cd189f31c sickcodes/docker-osx:big-sur "/bin/bash -c 'sudo …" 9 hours ago Exited (1) 36 seconds ago wonderful_edison ``` I'm not pretty sure if that's exact the problem, but that was probably the only abnormal thing I did the last time I ran it. Is there anything I can do to recover it? Thanks

adam closed this issue

2025-12-29 05:24:24 +01:00

adam commented

2025-12-29 05:24:26 +01:00

@Enzodtz commented on GitHub (May 26, 2021):

Seems that my disk was full, emptying it solved. Thanks

@Enzodtz commented on GitHub (May 26, 2021): Seems that my disk was full, emptying it solved. Thanks

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/Docker-OSX-sickcodes#193