docker crashes frequently on startup
This is the crash stack from the docker logs:
.....
2019-01-13 13:05:13.434372-0800 localhost com.docker.hyperkit[2914]: [ 0.105693] Speculative Store Bypass: Vulnerable
2019-01-13 13:05:13.577543-0800 localhost com.docker.hyperkit[2914]: [ 0.249247] Freeing SMP alternatives memory: 20K
2019-01-13 13:05:13.707308-0800 localhost com.docker.hyperkit[2914]: [ 0.376386] ftrace: allocating 35645 entries in 140 pages
2019-01-13 13:05:15.855677-0800 localhost com.docker.hyperkit[2914]: [ 2.532161] smpboot: Max logical packages: 2
2019-01-13 13:05:15.882920-0800 localhost com.docker.hyperkit[2914]: [ 2.557769] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
2019-01-13 13:05:15.992164-0800 localhost com.docker.hyperkit[2914]: [ 2.666219] ..MP-BIOS bug: 8254 timer not connected to IO-APIC
2019-01-13 13:05:15.998739-0800 localhost com.docker.hyperkit[2914]: [ 2.673452] ...trying to set up timer (IRQ0) through the 8259A ...
2019-01-13 13:05:16.003099-0800 localhost com.docker.hyperkit[2914]: [ 2.680027] ..... (found apic 0 pin 2) ...
2019-01-13 13:05:16.108382-0800 localhost com.docker.hyperkit[2914]: [ 2.786819] ....... failed.
2019-01-13 13:05:16.114403-0800 localhost com.docker.hyperkit[2914]: [ 2.789899] ...trying to set up timer as Virtual Wire IRQ...
2019-01-13 13:05:16.218349-0800 localhost com.docker.hyperkit[2914]: [ 2.896338] ..... failed.
2019-01-13 13:05:16.224222-0800 localhost com.docker.hyperkit[2914]: [ 2.900103] ...trying to set up timer as ExtINT IRQ...
2019-01-13 13:05:16.442003-0800 localhost com.docker.hyperkit[2914]: [ 3.121066] ..... failed :(.
2019-01-13 13:05:16.456839-0800 localhost com.docker.hyperkit[2914]: [ 3.125149] Kernel panic - not syncing: IO-APIC + timer doesn't work! Boot with apic=debug and send a report. Then try booting with the 'noapic' option.
2019-01-13 13:05:16.458492-0800 localhost com.docker.hyperkit[2914]: [ 3.125149]
2019-01-13 13:05:16.465514-0800 localhost com.docker.hyperkit[2914]: [ 3.140709] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.9.125-linuxkit #1
2019-01-13 13:05:16.471039-0800 localhost com.docker.hyperkit[2914]: [ 3.147726] Hardware name: BHYVE, BIOS 1.00 03/14/2014
2019-01-13 13:05:16.480892-0800 localhost com.docker.hyperkit[2914]: [ 3.153287] 0000000000000000 ffffffffaf420789 0000000000000000 ffffbab400007e30
2019-01-13 13:05:16.490131-0800 localhost com.docker.hyperkit[2914]: [ 3.163238] ffffffffaf19fbf5 0000000000000008 ffffbab400007e40 ffffbab400007dd8
2019-01-13 13:05:16.501249-0800 localhost com.docker.hyperkit[2914]: [ 3.172450] ca7f16cd286c8b68 0000000000000008 ffffbab400007e58 0000000000000000
2019-01-13 13:05:16.504028-0800 localhost com.docker.hyperkit[2914]: [ 3.183596] Call Trace:
2019-01-13 13:05:16.509580-0800 localhost com.docker.hyperkit[2914]: [ 3.186327] [
what kind of system are you running this on?
This happens frequently when running docker inside a macOS VM on a Mac Pro machine. I know that kvm/vmware expose timing virtiaulization features in CPUID instruction, so Linux could handle timing properly. I think you should implement this as well so Linux won't complain about timing.