Container not responding #58

New Issue

2025-12-28T23:22:46+01:00

adam commented

2025-12-28 23:22:46 +01:00

Originally created by @FaiqOsitech on GitHub (Jul 15, 2020).

After installation when i use the command.

start docker <containter_id>

container_id is printed in the next line and that's it. The container doesn't response.

Originally created by @FaiqOsitech on GitHub (Jul 15, 2020). After installation when i use the command. start docker <containter_id> container_id is printed in the next line and that's it. The container doesn't response.

adam closed this issue

2025-12-28 23:22:46 +01:00

adam commented

2025-12-28 23:22:47 +01:00

@Cerealkillerway commented on GitHub (Jul 15, 2020):

for me the problem were the permissions for the kvm folder; it looks like they are resetted every time so before running the container I always have to sudo chmod 666 /dev/kvm (I run on ubuntu)

then I can docker start <containerID>

@Cerealkillerway commented on GitHub (Jul 15, 2020): for me the problem were the permissions for the `kvm` folder; it looks like they are resetted every time so before running the container I always have to `sudo chmod 666 /dev/kvm` (I run on ubuntu) then I can `docker start <containerID>`

adam commented

2025-12-28 23:22:47 +01:00

@FaiqOsitech commented on GitHub (Jul 15, 2020):

i do run this command sudo chmod 666 /dev/kvm

and then i start the docker but still nothing happens.

@FaiqOsitech commented on GitHub (Jul 15, 2020): i do run this command sudo chmod 666 /dev/kvm and then i start the docker but still nothing happens.

adam commented

2025-12-28 23:22:47 +01:00

@stephane-r commented on GitHub (Jul 16, 2020):

I've the same result if i try to run the containerId using docker start <containerID>.

My kvm folder have correct chmod too.

@stephane-r commented on GitHub (Jul 16, 2020): I've the same result if i try to run the containerId using `docker start <containerID>`. My kvm folder have correct chmod too.

adam commented

2025-12-28 23:22:48 +01:00

@sickcodes commented on GitHub (Jul 16, 2020):

Most likely the wrong image being started.

If you don’t want to look for it, use the command in the readme to in the file path of the big .img

Cut and paste it somewhere as root

Start a new container, record the docker ps container id

Stop the container

Paste the img into the new one as root. Find the overlay path using the docker inspect

Or use docker cp if you have disk space

@sickcodes commented on GitHub (Jul 16, 2020): Most likely the wrong image being started. If you don’t want to look for it, use the command in the readme to in the file path of the big .img Cut and paste it somewhere as root Start a new container, record the docker ps container id Stop the container Paste the img into the new one as root. Find the overlay path using the docker inspect Or use docker cp if you have disk space

adam commented

2025-12-28 23:22:48 +01:00

@FaiqOsitech commented on GitHub (Jul 16, 2020):

Already tried that.

Still same thing happens.

@FaiqOsitech commented on GitHub (Jul 16, 2020): Already tried that. Still same thing happens.

adam commented

2025-12-28 23:22:48 +01:00

@stephane-r commented on GitHub (Jul 16, 2020):

Paste the img into the new one as root. Find the overlay path using the docker inspect

Have you more information about this step ?

@stephane-r commented on GitHub (Jul 16, 2020): `Paste the img into the new one as root. Find the overlay path using the docker inspect` Have you more information about this step ?

adam commented

2025-12-28 23:22:49 +01:00

@sickcodes commented on GitHub (Jul 20, 2020):

find the right image (usually the big one)
sudo find /var/lib/docker -size +10G | grep mac_hdd_ng.img

sudo move it somewhere

start a new docker
docker run --privileged -e "DISPLAY=${DISPLAY:-:0.0}" -v /tmp/.X11-unix:/tmp/.X11-unix sickcodes/docker-osx

copy its id into clipboard
docker ps

kill it
docker kill abc123efg

find your container's root folder
docker inspect abc123efg | grep Upper

put the old .img file in there

sudo mv \
/var/lib/docker/overlay2/ajjajajajaja/diff/home/arch/OSX-KVM/mac_hdd_ng.img \
/var/lib/docker/overlay2/yjyjyjyjjyyjy/diff/home/arch/OSX-KVM/mac_hdd_ng.img

@sickcodes commented on GitHub (Jul 20, 2020): find the right image (usually the big one) sudo find /var/lib/docker -size +10G | grep mac_hdd_ng.img sudo move it somewhere start a new docker `docker run --privileged -e "DISPLAY=${DISPLAY:-:0.0}" -v /tmp/.X11-unix:/tmp/.X11-unix sickcodes/docker-osx` copy its id into clipboard `docker ps` kill it `docker kill abc123efg` find your container's root folder `docker inspect abc123efg | grep Upper` put the old .img file in there ``` sudo mv \ /var/lib/docker/overlay2/ajjajajajaja/diff/home/arch/OSX-KVM/mac_hdd_ng.img \ /var/lib/docker/overlay2/yjyjyjyjjyyjy/diff/home/arch/OSX-KVM/mac_hdd_ng.img ```

adam commented

2025-12-28 23:22:49 +01:00

@c1tt1 commented on GitHub (Jul 26, 2020):

I had the same issue and it wasn't a matter of starting the wrong container, sudo chmod 666 /dev/kvm did nothing to help.

After several try failure, started a new container.

@c1tt1 commented on GitHub (Jul 26, 2020): I had the same issue and it wasn't a matter of starting the wrong container, `sudo chmod 666 /dev/kvm` did nothing to help. After several try failure, started a new container.

adam commented

2025-12-28 23:22:49 +01:00

@sickcodes commented on GitHub (Jul 27, 2020):

After you started a new container, you can move the old .img file into the new one and boot up into your previous installation by moving it into the new container’s directory

@sickcodes commented on GitHub (Jul 27, 2020): After you started a new container, you can move the old .img file into the new one and boot up into your previous installation by moving it into the new container’s directory

adam commented

2025-12-28 23:22:49 +01:00

@sickcodes commented on GitHub (Oct 7, 2020):

Closing this issue as you've mentioned it was solved in a new container

@sickcodes commented on GitHub (Oct 7, 2020): Closing this issue as you've mentioned it was solved in a new container

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/Docker-OSX#58