Failed to run with junos-vmx-x86-64-21.1R1.11.qcow2 - 1 failed system dependencies. Terminating

[narutaro]

Failing to run with junos-vmx-x86-64-21.1R1.11.qcow2. Could you give me some advice?

$ docker logs 01c5ca503af4
Juniper Networks vMX Docker Light Container

Linux 01c5ca503af4 5.4.0-1038-aws #40~18.04.1-Ubuntu SMP Sat Feb 6 01:56:56 UTC 2021 x86_64

CPU Model ................................ Intel(R) Xeon(R) Platinum 8124M CPU @ 3.00GHz
CPU affinity of this container ........... 0-7
KVM hardware virtualization extension .... no
Check http://www.linux-kvm.org/page/FAQ

Total System Memory ...................... 15 GB
Free Hugepages ........................... yes (8 x 1024 MB = 8192 MB)
Check for container privileged mode ...... yes
Check for sudo/root privileges ........... yes
Loop mount filesystem capability ......... yes
docker access ............................ CONTAINER ID        IMAGE                                   COMMAND             CREATED             STATUS                  PORTS                                           NAMES
01c5ca503af4        juniper/openjnpr-container-vmx:bionic   "/launch.sh"        1 second ago        Up Less than a second   0.0.0.0:32781->22/tcp, 0.0.0.0:32780->830/tcp   openjnprcontainervmx_vmx1_1
yes

lcpu affinity ............................  0-7

NUMA node(s):        1
NUMA node0 CPU(s):   0-7

1 failed system dependencies. Terminating

$ cat docker-compose.yml 
# Copyright (c) 2017, Juniper Networks, Inc.
# # All rights reserved.
#
version: "3"

services:

  vmx1:
    image: juniper/openjnpr-container-vmx:bionic
    privileged: true
    tty: true
    stdin_open: true
    ports:
      - "22"
      - "830"
    environment:
      - ID=vmx1
      - LICENSE=license-eval.txt
      - IMAGE=junos-vmx-x86-64-21.1R1.11.qcow2
      - PUBLICKEY=id_rsa.pub
      - CONFIG=vmx1.conf
        #      - WAITFOR=eth4
      - IO_CORE=2
      - WORKER_CORE=3
      - MASTER_CORE=4
      - VMXT_CORE=5
#      - HDDIMAGE=/images/p1.qcow2 # if we want it to be persistant
    volumes:
#      - $PWD/images:/images
      - $PWD:/u:ro
      - /var/run/docker.sock:/var/run/docker.sock
    networks:
      mgmt:
      net-a:
      net-b:
      net-c:

networks:
  mgmt:
  net-a:
  net-b:
  net-c:

$ uname -a
Linux ip-172-31-7-137 5.4.0-1038-aws #40~18.04.1-Ubuntu SMP Sat Feb 6 01:56:56 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

$ docker-compose version
docker-compose version 1.17.1, build unknown
docker-py version: 2.5.1
CPython version: 2.7.17
OpenSSL version: OpenSSL 1.1.1  11 Sep 2018
ubuntu@ip-172-31-7-137:~/OpenJNPR-Container-vMX$ docker version
Client:
 Version:           19.03.6
 API version:       1.40
 Go version:        go1.12.17
 Git commit:        369ce74a3c
 Built:             Fri Dec 18 12:21:44 2020
 OS/Arch:           linux/amd64
 Experimental:      false

Server:
 Engine:
  Version:          19.03.6
  API version:      1.40 (minimum version 1.12)
  Go version:       go1.12.17
  Git commit:       369ce74a3c
  Built:            Thu Dec 10 13:23:49 2020
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.3.3-0ubuntu1~18.04.4
  GitCommit:        
 runc:
  Version:          spec: 1.0.1-dev
  GitCommit:        
 docker-init:
  Version:          0.18.0
  GitCommit:        

[mwiget]

Your host doesn't allow the hypervisor (KVM) to run:

KVM hardware virtualization extension .... no
Check http://www.linux-kvm.org/page/FAQ

Typically a BIOS setting that needs to change (enable KVM). If you run nested (already in a VM), then that's not recommended, as it will be very slow. Anyhow, it requires enabling/allowing KVM.

[narutaro]

Thank you @mwiget. I will give it a try!