mirror of
https://github.com/sickcodes/Docker-OSX.git
synced 2026-01-11 21:10:25 +01:00
Container not responding #58
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.
@Cerealkillerway commented on GitHub (Jul 15, 2020):
for me the problem were the permissions for the
kvmfolder; it looks like they are resetted every time so before running the container I always have tosudo chmod 666 /dev/kvm(I run on ubuntu)then I can
docker start <containerID>@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.
@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.
@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
@FaiqOsitech commented on GitHub (Jul 16, 2020):
Already tried that.
Still same thing happens.
@stephane-r commented on GitHub (Jul 16, 2020):
Paste the img into the new one as root. Find the overlay path using the docker inspectHave you more information about this step ?
@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-osxcopy its id into clipboard
docker pskill it
docker kill abc123efgfind your container's root folder
docker inspect abc123efg | grep Upperput the old .img file in there
@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/kvmdid nothing to help.After several try failure, started a new container.
@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 (Oct 7, 2020):
Closing this issue as you've mentioned it was solved in a new container