mirror of
https://github.com/sickcodes/Docker-OSX.git
synced 2026-01-13 13:53:28 +01:00
Installing hangs and container becomes dead #219
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 @akshayde85 on GitHub (Jul 7, 2021).
Hello,
While installing the OS, after doing partition, it went smooth till "3 Min Remaining' dialogue but after that it reboots and moves no where. I have tried it multiple times suspecting docker issue and even manually updated it to latest stable above of snap with deleting the inactive containers, but nothing helps. Below are the snapshots of system and applications >
Linux declut 5.8.0-59-generic #66~20.04.1-Ubuntu SMP Thu Jun 17 11:14:10 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
:0
[sudo] password for heyeven:
1
NAME="Ubuntu"
PRETTY_NAME="Ubuntu 20.04.2 LTS"
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal
Filesystem Size Used Avail Use% Mounted on
/dev/nvme0n1p2 457G 69G 366G 16% /
QEMU emulator version 6.0.50 (v6.0.0-2231-g73c8bf4ccf)
Copyright (c) 2003-2021 Fabrice Bellard and the QEMU Project developers
libvirtd (libvirt) 6.0.0
total used free shared buff/cache available
Mem: 31Gi 1.8Gi 17Gi 100Mi 11Gi 28Gi
Swap: 2.0Gi 0B 2.0Gi
6
12
crw-rw----+ 1 heyeven heyeven 10, 232 Jul 7 14:40 /dev/kvm
total 32K
drwxrwxrwt 2 root root 4.0K Jul 7 08:38 .
drwxrwxrwt 24 root root 24K Jul 7 14:42 ..
srwxrwxrwx 1 heyeven heyeven 0 Jul 7 08:38 X0
srwxrwxr-x 1 gdm gdm 0 Jul 7 08:38 X1024
srwxrwxr-x 1 gdm gdm 0 Jul 7 08:38 X1025
root 1866 0.0 0.2 1169000 90628 ? Ssl 14:08 0:00 /usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock
heyeven 7683 0.0 0.0 17672 732 pts/0 S+ 14:48 0:00 grep --color=auto dockerd
kvm:x:108:
libvirt:x:136:heyeven
libvirt-qemu:x:64055:libvirt-qemu
libvirt-dnsmasq:x:137:
docker:x:1001:heyeven
#docker -v
Docker version 20.10.7, build f0df350
#qemu-system-x86_64 --version
QEMU emulator version 6.0.50 (v6.0.0-2231-g73c8bf4ccf)
Copyright (c) 2003-2021 Fabrice Bellard and the QEMU Project developers
#docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
#docker ps --all --filter "ancestor=sickcodes/docker-osx"
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
b34316a4d731 sickcodes/docker-osx "/bin/bash -c 'sudo …" 28 minutes ago Exited (0) 12 seconds ago stupefied_sutherland
669411735dfd sickcodes/docker-osx "/bin/bash -c 'sudo …" 14 hours ago Exited (0) 14 hours ago awesome_almeida
Error >
#docker run --privileged --net host --cap-add=ALL -v /tmp/.X11-unix:/tmp/.X11-unix -v /dev:/dev -v /lib/modules:/lib/modules sickcodes/docker-osx
ssh-keygen: generating new host keys: RSA DSA ECDSA ED25519
++ id -u
++ id -g
++ id -u
++ id -g
++ id -u
++ id -g
qemu-system-x86_64: -drive if=pflash,format=raw,readonly,file=/home/arch/OSX-KVM/OVMF_CODE.fd: warning: short-form boolean option 'readonly' deprecated
Please use readonly=on instead
QEMU 6.0.0 monitor - type 'help' for more information
(qemu) qemu-system-x86_64: Slirp: Failed to send packet, ret: -1
qemu-system-x86_64: Slirp: Failed to send packet, ret: -1
@akshayde85 commented on GitHub (Jul 7, 2021):
On side note couple of points >
@sickcodes commented on GitHub (Jul 9, 2021):
The reboot phase is part of the installation, I am testing installation right now anyway
@linsui commented on GitHub (Oct 21, 2021):
I have the same issue on all of Catalina, Big Sur and Monterey.
@linsui commented on GitHub (Oct 22, 2021):
The problem is just that the VM can't restart itself. I can close qemu and run docker start manully.
@akshayde85 commented on GitHub (Oct 22, 2021):
Check your RAM. One of mine was faulty and was causing the issue. Now i did
On Fri, Oct 22, 2021, 10:35 linsui @.***> wrote:
@linsui commented on GitHub (Oct 22, 2021):
Do you mean the RAM of the VM? How to do that? I'm not familiar with MacOS.
@akshayde85 commented on GitHub (Oct 22, 2021):
No RAM of your machine. See i had 2 sticks of 16gigs each out of that one had issues and always throwed some weird memory errors on other VMs as well ( i noticed this late) so I replaced it by doing memtest86 on each individual RAM to detect which one was faulty.
In general when you install macos on any vm or standalone system, it downloads and compiles(i believe) complete OS package to check for any issues. At this time, if your RAM or any component of hardware have issues, then this will not work. The reason being when apple ships Mac's, complete hardware set is tested but again when "You" do it, the complete testing part falls on your shoulder.
Give a try to check Memory or graphic card of your system if they are working correctly(might work on Windows or Linux but not on apple).
@linsui commented on GitHub (Oct 22, 2021):
Since I have only one RAM I believe it works well. In fact, macos works well. The only problem is that it can't reboot the VM during installation. I doubt there are some issues in qemu.
@marcesengel commented on GitHub (Nov 16, 2021):
@linsui @sickcodes I've got the same problem - QEMU somehow seems to fail restarting the machine. Restarting manually works and the installation appears to be successful using manual restarts.
However I've been suspecting one of my RAM sticks to be faulty for a long time, will check this evening and report back.
@sickcodes commented on GitHub (Nov 18, 2021):
Sometimes at the very end of the install, it's successful, but doesn't restart. Still works though, can't confirm why though 😂