* Adding Docker to NXP Image fails to execute run on target
@ 2019-02-01 15:31 Coy, Russell
2019-02-07 15:03 ` Mark Asselstine
0 siblings, 1 reply; 3+ messages in thread
From: Coy, Russell @ 2019-02-01 15:31 UTC (permalink / raw)
To: meta-virtualization
[-- Attachment #1: Type: text/plain, Size: 6775 bytes --]
Hello all,
I am trying to add Docker to an image built under Yocto and hence am attempting to use the meta-virtualization layer.
The target processor is an NXP imx8mq evk board and I am basing everything on the NXP BSP v4.9.51, which is based on Yocto morty.
I have git cloned the morty branch of the meta-virtualization layer to the top level of our Yocto project and added the layer to the build/bblayers.conf file and added DISTRO_FEATURES_append = " virtualization" to the build/local.conf file. I have a custom layer with a custom image (based on core-image) that includes docker (i.e. IMAGE_INSTALL += " docker"). A complete re-build of the image using bitbake is successful, and when the image is transferred to the target (on an sd card) and booted, the docker daemon starts up OK. However if I then try running "docker run hello-world" to test out the installation, it will pull the hello-world image, but fails with a daemon error:
Unable to find image 'hello-world:latest' locally
latest: Pulling from library/hello-world
3b4173355427: Pulling fs layer
3b4173355427: Verifying Checksum
3b4173355427: Download complete
3b4173355427: Pull complete
Digest: sha256:2557e3c07ed1e38f26e389462d03ed943586f744621577a99efb77324b0fe535
Status: Downloaded newer image for hello-world:latest
docker: Error response from daemon: operation not supported.
See 'docker run --help'.
Other images give similar results (e.g. busybox or alpine).
It seems that the pull works, and images are downloaded OK, but they do not run.
I'd be grateful if you have any advice on how to get this branch of docker working?
For information:
"docker info" gives:
Containers: 0
Running: 0
Paused: 0
Stopped: 0
Images: 1
Server Version: 1.12.5
Storage Driver: overlay
Backing Filesystem: extfs
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: host bridge overlay null
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Security Options:
Kernel Version: 4.9.51-imx_4.9.51_imx8m_ga+g6df7474
Operating System: NXP i.MX Release Distro 4.9.51-mx8-ga (morty)
OSType: linux
Architecture: aarch64
CPUs: 4
Total Memory: 2.928 GiB
Name: Test-imx8
ID: L4G3:4SLL:UO75:25FS:6OO6:NOPG:SGF7:DXVC:GN5P:7DZK:4O2D:3K4L
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Insecure Registries:
http://localhost:5000
127.0.0.0/8
Downloading and running "check-config.sh" gives:
info: reading kernel config from /proc/config.gz ...
Generally Necessary:
- cgroup hierarchy: properly mounted [/sys/fs/cgroup]
- CONFIG_NAMESPACES: enabled
- CONFIG_NET_NS: enabled
- CONFIG_PID_NS: enabled
- CONFIG_IPC_NS: enabled
- CONFIG_UTS_NS: enabled
- CONFIG_CGROUPS: enabled
- CONFIG_CGROUP_CPUACCT: enabled
- CONFIG_CGROUP_DEVICE: enabled
- CONFIG_CGROUP_FREEZER: missing
- CONFIG_CGROUP_SCHED: enabled
- CONFIG_CPUSETS: enabled
- CONFIG_MEMCG: enabled
- CONFIG_KEYS: enabled
- CONFIG_VETH: enabled (as module)
- CONFIG_BRIDGE: enabled (as module)
- CONFIG_BRIDGE_NETFILTER: enabled (as module)
- CONFIG_NF_NAT_IPV4: enabled (as module)
- CONFIG_IP_NF_FILTER: enabled (as module)
- CONFIG_IP_NF_TARGET_MASQUERADE: enabled (as module)
- CONFIG_NETFILTER_XT_MATCH_ADDRTYPE: enabled (as module)
- CONFIG_NETFILTER_XT_MATCH_CONNTRACK: enabled (as module)
- CONFIG_NETFILTER_XT_MATCH_IPVS: missing
- CONFIG_IP_NF_NAT: enabled (as module)
- CONFIG_NF_NAT: enabled (as module)
- CONFIG_NF_NAT_NEEDED: enabled
- CONFIG_POSIX_MQUEUE: enabled
Optional Features:
- CONFIG_USER_NS: enabled
- CONFIG_SECCOMP: enabled
- CONFIG_CGROUP_PIDS: enabled
- CONFIG_MEMCG_SWAP: enabled
- CONFIG_MEMCG_SWAP_ENABLED: enabled
(cgroup swap accounting is currently enabled)
- CONFIG_BLK_CGROUP: enabled
- CONFIG_BLK_DEV_THROTTLING: missing
- CONFIG_IOSCHED_CFQ: enabled
- CONFIG_CFQ_GROUP_IOSCHED: missing
- CONFIG_CGROUP_PERF: enabled
- CONFIG_CGROUP_HUGETLB: enabled
- CONFIG_NET_CLS_CGROUP: missing
- CONFIG_CGROUP_NET_PRIO: missing
- CONFIG_CFS_BANDWIDTH: missing
- CONFIG_FAIR_GROUP_SCHED: enabled
- CONFIG_RT_GROUP_SCHED: missing
- CONFIG_IP_NF_TARGET_REDIRECT: missing
- CONFIG_IP_VS: missing
- CONFIG_IP_VS_NFCT: missing
- CONFIG_IP_VS_PROTO_TCP: missing
- CONFIG_IP_VS_PROTO_UDP: missing
- CONFIG_IP_VS_RR: missing
- CONFIG_EXT3_FS: enabled
- CONFIG_EXT3_FS_XATTR: missing
- CONFIG_EXT3_FS_POSIX_ACL: missing
- CONFIG_EXT3_FS_SECURITY: missing
(enable these ext3 configs if you are using ext3 as backing filesystem)
- CONFIG_EXT4_FS: enabled
- CONFIG_EXT4_FS_POSIX_ACL: enabled
- CONFIG_EXT4_FS_SECURITY: missing
enable these ext4 configs if you are using ext4 as backing filesystem
- Network Drivers:
- "overlay":
- CONFIG_VXLAN: missing
Optional (for encrypted networks):
- CONFIG_CRYPTO: enabled
- CONFIG_CRYPTO_AEAD: enabled
- CONFIG_CRYPTO_GCM: enabled
- CONFIG_CRYPTO_SEQIV: enabled
- CONFIG_CRYPTO_GHASH: enabled
- CONFIG_XFRM: enabled
- CONFIG_XFRM_USER: missing
- CONFIG_XFRM_ALGO: missing
- CONFIG_INET_ESP: missing
- CONFIG_INET_XFRM_MODE_TRANSPORT: enabled
- "mipvlan":
- CONFIG_IPVLAN: missing
- "macvlan":
- CONFIG_MACVLAN: enabled (as module)
- CONFIG_DUMMY: missing
- "ftp,tftp client in container":
- CONFIG_NF_NAT_FTP: missing
- CONFIG_NF_CONNTRACK_FTP: missing
- CONFIG_NF_NAT_TFTP: missing
- CONFIG_NF_CONNTRACK_TFTP: missing
- Storage Drivers:
- "aufs":
- CONFIG_AUFS_FS: missing
- "btrfs":
- CONFIG_BTRFS_FS: enabled (as module)
- CONFIG_BTRFS_FS_POSIX_ACL: enabled
- "devicemapper":
- CONFIG_BLK_DEV_DM: missing
- CONFIG_DM_THIN_PROVISIONING: missing
- "overlay":
- CONFIG_OVERLAY_FS: enabled (as module)
- "zfs":
- /dev/zfs: missing
- zfs command: missing
- zpool command: missing
Limits:
- /proc/sys/kernel/keys/root_maxkeys: 1000000
"docker -version" gives:
Docker version 1.12.5, build 7392c3b
From the config output, I see that some variables are not enabled. Could this be an issue?
Kind regards,
Russell
________________________________________
Roke Manor Research Limited, Romsey, Hampshire, SO51 0ZN, United Kingdom.Part of the Chemring Group.
Registered in England & Wales. Registered No: 00267550
http://www.roke.co.uk
_______________________________________
The information contained in this e-mail and any attachments is proprietary to Roke Manor Research Limited and
must not be passed to any third party without permission. This communication is for information only and shall
not create or change any contractual relationship.
________________________________________
[-- Attachment #2: Type: text/html, Size: 15839 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: Adding Docker to NXP Image fails to execute run on target 2019-02-01 15:31 Adding Docker to NXP Image fails to execute run on target Coy, Russell @ 2019-02-07 15:03 ` Mark Asselstine 2019-02-11 9:59 ` Coy, Russell 0 siblings, 1 reply; 3+ messages in thread From: Mark Asselstine @ 2019-02-07 15:03 UTC (permalink / raw) To: Coy, Russell; +Cc: meta-virtualization On Fri, Feb 1, 2019 at 10:31 AM Coy, Russell <russell.coy@roke.co.uk> wrote: > > Hello all, > > I am trying to add Docker to an image built under Yocto and hence am attempting to use the meta-virtualization layer. > > The target processor is an NXP imx8mq evk board and I am basing everything on the NXP BSP v4.9.51, which is based on Yocto morty. > > I have git cloned the morty branch of the meta-virtualization layer to the top level of our Yocto project and added the layer to the build/bblayers.conf file and added DISTRO_FEATURES_append = " virtualization" to the build/local.conf file. I have a custom layer with a custom image (based on core-image) that includes docker (i.e. IMAGE_INSTALL += " docker”). A complete re-build of the image using bitbake is successful, and when the image is transferred to the target (on an sd card) and booted, the docker daemon starts up OK. However if I then try running “docker run hello-world” to test out the installation, it will pull the hello-world image, but fails with a daemon error: > > Unable to find image 'hello-world:latest' locally > > latest: Pulling from library/hello-world > > 3b4173355427: Pulling fs layer > > 3b4173355427: Verifying Checksum > > 3b4173355427: Download complete > > 3b4173355427: Pull complete > > Digest: sha256:2557e3c07ed1e38f26e389462d03ed943586f744621577a99efb77324b0fe535 > > Status: Downloaded newer image for hello-world:latest > > docker: Error response from daemon: operation not supported. This is what you need to focus on. Run docker with '--debug' review logs... you need to determine what operation is not supported. If after doing this you still can't determine what is wrong I usually recommend you get a known working configuration up and running which you can compare against. In this case configure another build, setup the bblayers.conf and setup your local.conf with --- MACHINE = "qemux86-64" DISTRO_FEATURES_append = " virtualization" IMAGE_INSTALL_append = "docker kernel-module-xt-conntrack kernel-module-nf-nat kernel-module-xt-addrtype" KERNEL_MODULE_AUTOLOAD += "xt_conntrack" KERNEL_MODULE_AUTOLOAD += "xt_addrtype" DISTRO_FEATURES_append = " systemd" DISTRO_FEATURES_BACKFILL_CONSIDERED += "sysvinit" VIRTUAL-RUNTIME_init_manager = "systemd" VIRTUAL-RUNTIME_initscripts = "systemd-compat-units" --- Run the image in QEMU and you should be able to run get the hello world container running. Then you can compare your non-working case with the working case. Mark > > See 'docker run --help'. > > Other images give similar results (e.g. busybox or alpine). > > It seems that the pull works, and images are downloaded OK, but they do not run. > > I’d be grateful if you have any advice on how to get this branch of docker working? > > For information: > > “docker info” gives: > > Containers: 0 > > Running: 0 > > Paused: 0 > > Stopped: 0 > > Images: 1 > > Server Version: 1.12.5 > > Storage Driver: overlay > > Backing Filesystem: extfs > > Logging Driver: json-file > > Cgroup Driver: cgroupfs > > Plugins: > > Volume: local > > Network: host bridge overlay null > > Swarm: inactive > > Runtimes: runc > > Default Runtime: runc > > Security Options: > > Kernel Version: 4.9.51-imx_4.9.51_imx8m_ga+g6df7474 > > Operating System: NXP i.MX Release Distro 4.9.51-mx8-ga (morty) > > OSType: linux > > Architecture: aarch64 > > CPUs: 4 > > Total Memory: 2.928 GiB > > Name: Test-imx8 > > ID: L4G3:4SLL:UO75:25FS:6OO6:NOPG:SGF7:DXVC:GN5P:7DZK:4O2D:3K4L > > Docker Root Dir: /var/lib/docker > > Debug Mode (client): false > > Debug Mode (server): false > > Registry: https://index.docker.io/v1/ > > Insecure Registries: > > http://localhost:5000 > > 127.0.0.0/8 > > Downloading and running “check-config.sh” gives: > > info: reading kernel config from /proc/config.gz ... > > Generally Necessary: > > - cgroup hierarchy: properly mounted [/sys/fs/cgroup] > > - CONFIG_NAMESPACES: enabled > > - CONFIG_NET_NS: enabled > > - CONFIG_PID_NS: enabled > > - CONFIG_IPC_NS: enabled > > - CONFIG_UTS_NS: enabled > > - CONFIG_CGROUPS: enabled > > - CONFIG_CGROUP_CPUACCT: enabled > > - CONFIG_CGROUP_DEVICE: enabled > > - CONFIG_CGROUP_FREEZER: missing > > - CONFIG_CGROUP_SCHED: enabled > > - CONFIG_CPUSETS: enabled > > - CONFIG_MEMCG: enabled > > - CONFIG_KEYS: enabled > > - CONFIG_VETH: enabled (as module) > > - CONFIG_BRIDGE: enabled (as module) > > - CONFIG_BRIDGE_NETFILTER: enabled (as module) > > - CONFIG_NF_NAT_IPV4: enabled (as module) > > - CONFIG_IP_NF_FILTER: enabled (as module) > > - CONFIG_IP_NF_TARGET_MASQUERADE: enabled (as module) > > - CONFIG_NETFILTER_XT_MATCH_ADDRTYPE: enabled (as module) > > - CONFIG_NETFILTER_XT_MATCH_CONNTRACK: enabled (as module) > > - CONFIG_NETFILTER_XT_MATCH_IPVS: missing > > - CONFIG_IP_NF_NAT: enabled (as module) > > - CONFIG_NF_NAT: enabled (as module) > > - CONFIG_NF_NAT_NEEDED: enabled > > - CONFIG_POSIX_MQUEUE: enabled > > Optional Features: > > - CONFIG_USER_NS: enabled > > - CONFIG_SECCOMP: enabled > > - CONFIG_CGROUP_PIDS: enabled > > - CONFIG_MEMCG_SWAP: enabled > > - CONFIG_MEMCG_SWAP_ENABLED: enabled > > (cgroup swap accounting is currently enabled) > > - CONFIG_BLK_CGROUP: enabled > > - CONFIG_BLK_DEV_THROTTLING: missing > > - CONFIG_IOSCHED_CFQ: enabled > > - CONFIG_CFQ_GROUP_IOSCHED: missing > > - CONFIG_CGROUP_PERF: enabled > > - CONFIG_CGROUP_HUGETLB: enabled > > - CONFIG_NET_CLS_CGROUP: missing > > - CONFIG_CGROUP_NET_PRIO: missing > > - CONFIG_CFS_BANDWIDTH: missing > > - CONFIG_FAIR_GROUP_SCHED: enabled > > - CONFIG_RT_GROUP_SCHED: missing > > - CONFIG_IP_NF_TARGET_REDIRECT: missing > > - CONFIG_IP_VS: missing > > - CONFIG_IP_VS_NFCT: missing > > - CONFIG_IP_VS_PROTO_TCP: missing > > - CONFIG_IP_VS_PROTO_UDP: missing > > - CONFIG_IP_VS_RR: missing > > - CONFIG_EXT3_FS: enabled > > - CONFIG_EXT3_FS_XATTR: missing > > - CONFIG_EXT3_FS_POSIX_ACL: missing > > - CONFIG_EXT3_FS_SECURITY: missing > > (enable these ext3 configs if you are using ext3 as backing filesystem) > > - CONFIG_EXT4_FS: enabled > > - CONFIG_EXT4_FS_POSIX_ACL: enabled > > - CONFIG_EXT4_FS_SECURITY: missing > > enable these ext4 configs if you are using ext4 as backing filesystem > > - Network Drivers: > > - "overlay": > > - CONFIG_VXLAN: missing > > Optional (for encrypted networks): > > - CONFIG_CRYPTO: enabled > > - CONFIG_CRYPTO_AEAD: enabled > > - CONFIG_CRYPTO_GCM: enabled > > - CONFIG_CRYPTO_SEQIV: enabled > > - CONFIG_CRYPTO_GHASH: enabled > > - CONFIG_XFRM: enabled > > - CONFIG_XFRM_USER: missing > > - CONFIG_XFRM_ALGO: missing > > - CONFIG_INET_ESP: missing > > - CONFIG_INET_XFRM_MODE_TRANSPORT: enabled > > - "mipvlan": > > - CONFIG_IPVLAN: missing > > - "macvlan": > > - CONFIG_MACVLAN: enabled (as module) > > - CONFIG_DUMMY: missing > > - "ftp,tftp client in container": > > - CONFIG_NF_NAT_FTP: missing > > - CONFIG_NF_CONNTRACK_FTP: missing > > - CONFIG_NF_NAT_TFTP: missing > > - CONFIG_NF_CONNTRACK_TFTP: missing > > - Storage Drivers: > > - "aufs": > > - CONFIG_AUFS_FS: missing > > - "btrfs": > > - CONFIG_BTRFS_FS: enabled (as module) > > - CONFIG_BTRFS_FS_POSIX_ACL: enabled > > - "devicemapper": > > - CONFIG_BLK_DEV_DM: missing > > - CONFIG_DM_THIN_PROVISIONING: missing > > - "overlay": > > - CONFIG_OVERLAY_FS: enabled (as module) > > - "zfs": > > - /dev/zfs: missing > > - zfs command: missing > > - zpool command: missing > > Limits: > > - /proc/sys/kernel/keys/root_maxkeys: 1000000 > > “docker –version” gives: > > Docker version 1.12.5, build 7392c3b > > From the config output, I see that some variables are not enabled. Could this be an issue? > > Kind regards, > > Russell > > > > Follow Us: LinkedIn | Twitter | Facebook > > Roke Manor Research Limited, Romsey, Hampshire, SO51 0ZN, United Kingdom. Part of the Chemring Group. Registered in England & Wales. Registered No: 00267550. The information contained in this e-mail and any attachments is proprietary to Roke Manor Research Limited and must not be passed to any third party without permission. This communication is for information only and shall not create or change any contractual relationship. > www.roke.co.uk > > ________________________________ > -- > _______________________________________________ > meta-virtualization mailing list > meta-virtualization@yoctoproject.org > https://lists.yoctoproject.org/listinfo/meta-virtualization ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Adding Docker to NXP Image fails to execute run on target 2019-02-07 15:03 ` Mark Asselstine @ 2019-02-11 9:59 ` Coy, Russell 0 siblings, 0 replies; 3+ messages in thread From: Coy, Russell @ 2019-02-11 9:59 UTC (permalink / raw) To: Mark Asselstine; +Cc: meta-virtualization [-- Attachment #1: Type: text/plain, Size: 14011 bytes --] Hi Mark, Thanks for the reply. I’ve had to stop pursuing adding Docker to the image at the present time, although I’m still poking around in my spare time. I’m not that familiar with Docker, so please forgive my ignorance. I’ve tried running “docker –debug run hello-world” and I get the following docker messages in the /var/logs/messages file: Feb 11 09:07:05 imx8mqevk daemon.info docker[2923]: time="2019-02-11T09:07:05.965795000Z" level=debug msg="Calling POST /v1.24/containers/create" Feb 11 09:07:05 imx8mqevk daemon.info docker[2923]: time="2019-02-11T09:07:05.966963000Z" level=debug msg="form data: {\"AttachStderr\":true,\"AttachStdin\":false,\"AttachStdout\":true,\"Cmd\":null,\"Domainname\":\"\",\"Entrypoint\":null,\"Env\":[],\"HostConfig\":{\"AutoRe Feb 11 09:07:05 imx8mqevk daemon.info docker[2923]: time="2019-02-11T09:07:05.972370000Z" level=error msg="Handler for POST /v1.24/containers/create returned error: No such image: hello-world:latest" Feb 11 09:07:05 imx8mqevk daemon.info docker[2923]: time="2019-02-11T09:07:05.976692000Z" level=debug msg="Calling GET /v1.24/info" Feb 11 09:07:05 imx8mqevk daemon.info docker[2923]: time="2019-02-11T09:07:05.986406000Z" level=debug msg="Calling POST /v1.24/images/create?fromImage=hello-world&tag=latest" Feb 11 09:07:05 imx8mqevk daemon.info docker[2923]: time="2019-02-11T09:07:05.992557000Z" level=debug msg="Trying to pull hello-world from http://localhost:5000/ v2" Feb 11 09:07:05 imx8mqevk daemon.info docker[2923]: time="2019-02-11T09:07:05.994871000Z" level=warning msg="Error getting v2 registry: Get http://localhost:5000/v2/: dial tcp [::1]:5000: getsockopt: connection refused" Feb 11 09:07:05 imx8mqevk daemon.info docker[2923]: time="2019-02-11T09:07:05.995485000Z" level=error msg="Attempting next endpoint for pull after error: Get http://localhost:5000/v2/: dial tcp [::1]:5000: getsockopt: connection refused" Feb 11 09:07:05 imx8mqevk daemon.info docker[2923]: time="2019-02-11T09:07:05.995943000Z" level=debug msg="Trying to pull hello-world from https://registry-1.docker.io v2" Feb 11 09:07:07 imx8mqevk daemon.info docker[2923]: time="2019-02-11T09:07:07.670991000Z" level=debug msg="Pulling ref from V2 registry: hello-world:latest" Feb 11 09:07:08 imx8mqevk daemon.info docker[2923]: time="2019-02-11T09:07:08.219396000Z" level=debug msg="pulling blob \"sha256:3b4173355427082b90463dbe6b9606a6a8c14c9d1235469c62dd95aba76da642\"" Feb 11 09:07:09 imx8mqevk daemon.info docker[2923]: time="2019-02-11T09:07:09.146664000Z" level=debug msg="Downloaded 3b4173355427 to tempfile /var/lib/docker/tmp/GetImageBlob562921062" Feb 11 09:07:09 imx8mqevk daemon.info docker[2923]: time="2019-02-11T09:07:09.158520000Z" level=debug msg="Start untar layer" Feb 11 09:07:09 imx8mqevk daemon.info docker[2923]: time="2019-02-11T09:07:09.260938000Z" level=debug msg="Untar time: 0.102355s" Feb 11 09:07:09 imx8mqevk daemon.info docker[2923]: time="2019-02-11T09:07:09.261160000Z" level=debug msg="Failed to unmount 3e21879a79efb04c8092a3dbe024f0c408834c402efe9ef7bfb099a79209da1b overlay: no such file or directory" Feb 11 09:07:09 imx8mqevk daemon.info docker[2923]: time="2019-02-11T09:07:09.261320000Z" level=debug msg="Applied tar sha256:26d82c2b34c3dedc481b7db3d84c3d1892a6a82cd97624767c4217beb382e7f8 to 3e21879a79efb04c8092a3dbe024f0c408834c402efe9ef7bfb099a79209da1b, size: 4752" Feb 11 09:07:10 imx8mqevk daemon.info docker[2923]: time="2019-02-11T09:07:10.953758000Z" level=debug msg="Calling POST /v1.24/containers/create" Feb 11 09:07:10 imx8mqevk daemon.info docker[2923]: time="2019-02-11T09:07:10.956378000Z" level=debug msg="form data: {\"AttachStderr\":true,\"AttachStdin\":false,\"AttachStdout\":true,\"Cmd\":null,\"Domainname\":\"\",\"Entrypoint\":null,\"Env\":[],\"HostConfig\":{\"AutoRe Feb 11 09:07:10 imx8mqevk daemon.info docker[2923]: time="2019-02-11T09:07:10.984999000Z" level=error msg="Handler for POST /v1.24/containers/create returned error: operation not supported" I presume this is the correct method. It looks like it cannot create the container. I’ve also added a ‘/etc’/docker/daemon.json’ file containing ‘{ “debug”: true }’, but I don’t see any docker debug logs in e.g. /var/lib/docker. I’ll try generating the QEMU image when I have some time. Kind regards, Russell From: Mark Asselstine [mailto:asselsm@gmail.com] Sent: 07 February 2019 15:03 To: Coy, Russell Cc: meta-virtualization@yoctoproject.org Subject: Re: [meta-virtualization] Adding Docker to NXP Image fails to execute run on target On Fri, Feb 1, 2019 at 10:31 AM Coy, Russell <russell.coy@roke.co.uk> wrote: > > Hello all, > > I am trying to add Docker to an image built under Yocto and hence am attempting to use the meta-virtualization layer. > > The target processor is an NXP imx8mq evk board and I am basing everything on the NXP BSP v4.9.51, which is based on Yocto morty. > > I have git cloned the morty branch of the meta-virtualization layer to the top level of our Yocto project and added the layer to the build/bblayers.conf file and added DISTRO_FEATURES_append = " virtualization" to the build/local.conf file. I have a custom layer with a custom image (based on core-image) that includes docker (i.e. IMAGE_INSTALL += " docker”). A complete re-build of the image using bitbake is successful, and when the image is transferred to the target (on an sd card) and booted, the docker daemon starts up OK. However if I then try running “docker run hello-world” to test out the installation, it will pull the hello-world image, but fails with a daemon error: > > Unable to find image 'hello-world:latest' locally > > latest: Pulling from library/hello-world > > 3b4173355427: Pulling fs layer > > 3b4173355427: Verifying Checksum > > 3b4173355427: Download complete > > 3b4173355427: Pull complete > > Digest: sha256:2557e3c07ed1e38f26e389462d03ed943586f744621577a99efb77324b0fe535 > > Status: Downloaded newer image for hello-world:latest > > docker: Error response from daemon: operation not supported. This is what you need to focus on. Run docker with '--debug' review logs... you need to determine what operation is not supported. If after doing this you still can't determine what is wrong I usually recommend you get a known working configuration up and running which you can compare against. In this case configure another build, setup the bblayers.conf and setup your local.conf with ________________________________________ Roke Manor Research Limited, Romsey, Hampshire, SO51 0ZN, United Kingdom.Part of the Chemring Group. Registered in England & Wales. Registered No: 00267550 http://www.roke.co.uk _______________________________________ The information contained in this e-mail and any attachments is proprietary to Roke Manor Research Limited and must not be passed to any third party without permission. This communication is for information only and shall not create or change any contractual relationship. ________________________________________ --- MACHINE = "qemux86-64" DISTRO_FEATURES_append = " virtualization" IMAGE_INSTALL_append = "docker kernel-module-xt-conntrack kernel-module-nf-nat kernel-module-xt-addrtype" KERNEL_MODULE_AUTOLOAD += "xt_conntrack" KERNEL_MODULE_AUTOLOAD += "xt_addrtype" DISTRO_FEATURES_append = " systemd" DISTRO_FEATURES_BACKFILL_CONSIDERED += "sysvinit" VIRTUAL-RUNTIME_init_manager = "systemd" VIRTUAL-RUNTIME_initscripts = "systemd-compat-units" --- Run the image in QEMU and you should be able to run get the hello world container running. Then you can compare your non-working case with the working case. Mark > > See 'docker run --help'. > > Other images give similar results (e.g. busybox or alpine). > > It seems that the pull works, and images are downloaded OK, but they do not run. > > I’d be grateful if you have any advice on how to get this branch of docker working? > > For information: > > “docker info” gives: > > Containers: 0 > > Running: 0 > > Paused: 0 > > Stopped: 0 > > Images: 1 > > Server Version: 1.12.5 > > Storage Driver: overlay > > Backing Filesystem: extfs > > Logging Driver: json-file > > Cgroup Driver: cgroupfs > > Plugins: > > Volume: local > > Network: host bridge overlay null > > Swarm: inactive > > Runtimes: runc > > Default Runtime: runc > > Security Options: > > Kernel Version: 4.9.51-imx_4.9.51_imx8m_ga+g6df7474 > > Operating System: NXP i.MX Release Distro 4.9.51-mx8-ga (morty) > > OSType: linux > > Architecture: aarch64 > > CPUs: 4 > > Total Memory: 2.928 GiB > > Name: Test-imx8 > > ID: L4G3:4SLL:UO75:25FS:6OO6:NOPG:SGF7:DXVC:GN5P:7DZK:4O2D:3K4L > > Docker Root Dir: /var/lib/docker > > Debug Mode (client): false > > Debug Mode (server): false > > Registry: https://index.docker.io/v1/<https://index.docker.io/v1/> > > Insecure Registries: > > http://localhost:5000 > > 127.0.0.0/8<http://127.0.0.0/8> > > Downloading and running “check-config.sh” gives: > > info: reading kernel config from /proc/config.gz ... > > Generally Necessary: > > - cgroup hierarchy: properly mounted [/sys/fs/cgroup] > > - CONFIG_NAMESPACES: enabled > > - CONFIG_NET_NS: enabled > > - CONFIG_PID_NS: enabled > > - CONFIG_IPC_NS: enabled > > - CONFIG_UTS_NS: enabled > > - CONFIG_CGROUPS: enabled > > - CONFIG_CGROUP_CPUACCT: enabled > > - CONFIG_CGROUP_DEVICE: enabled > > - CONFIG_CGROUP_FREEZER: missing > > - CONFIG_CGROUP_SCHED: enabled > > - CONFIG_CPUSETS: enabled > > - CONFIG_MEMCG: enabled > > - CONFIG_KEYS: enabled > > - CONFIG_VETH: enabled (as module) > > - CONFIG_BRIDGE: enabled (as module) > > - CONFIG_BRIDGE_NETFILTER: enabled (as module) > > - CONFIG_NF_NAT_IPV4: enabled (as module) > > - CONFIG_IP_NF_FILTER: enabled (as module) > > - CONFIG_IP_NF_TARGET_MASQUERADE: enabled (as module) > > - CONFIG_NETFILTER_XT_MATCH_ADDRTYPE: enabled (as module) > > - CONFIG_NETFILTER_XT_MATCH_CONNTRACK: enabled (as module) > > - CONFIG_NETFILTER_XT_MATCH_IPVS: missing > > - CONFIG_IP_NF_NAT: enabled (as module) > > - CONFIG_NF_NAT: enabled (as module) > > - CONFIG_NF_NAT_NEEDED: enabled > > - CONFIG_POSIX_MQUEUE: enabled > > Optional Features: > > - CONFIG_USER_NS: enabled > > - CONFIG_SECCOMP: enabled > > - CONFIG_CGROUP_PIDS: enabled > > - CONFIG_MEMCG_SWAP: enabled > > - CONFIG_MEMCG_SWAP_ENABLED: enabled > > (cgroup swap accounting is currently enabled) > > - CONFIG_BLK_CGROUP: enabled > > - CONFIG_BLK_DEV_THROTTLING: missing > > - CONFIG_IOSCHED_CFQ: enabled > > - CONFIG_CFQ_GROUP_IOSCHED: missing > > - CONFIG_CGROUP_PERF: enabled > > - CONFIG_CGROUP_HUGETLB: enabled > > - CONFIG_NET_CLS_CGROUP: missing > > - CONFIG_CGROUP_NET_PRIO: missing > > - CONFIG_CFS_BANDWIDTH: missing > > - CONFIG_FAIR_GROUP_SCHED: enabled > > - CONFIG_RT_GROUP_SCHED: missing > > - CONFIG_IP_NF_TARGET_REDIRECT: missing > > - CONFIG_IP_VS: missing > > - CONFIG_IP_VS_NFCT: missing > > - CONFIG_IP_VS_PROTO_TCP: missing > > - CONFIG_IP_VS_PROTO_UDP: missing > > - CONFIG_IP_VS_RR: missing > > - CONFIG_EXT3_FS: enabled > > - CONFIG_EXT3_FS_XATTR: missing > > - CONFIG_EXT3_FS_POSIX_ACL: missing > > - CONFIG_EXT3_FS_SECURITY: missing > > (enable these ext3 configs if you are using ext3 as backing filesystem) > > - CONFIG_EXT4_FS: enabled > > - CONFIG_EXT4_FS_POSIX_ACL: enabled > > - CONFIG_EXT4_FS_SECURITY: missing > > enable these ext4 configs if you are using ext4 as backing filesystem > > - Network Drivers: > > - "overlay": > > - CONFIG_VXLAN: missing > > Optional (for encrypted networks): > > - CONFIG_CRYPTO: enabled > > - CONFIG_CRYPTO_AEAD: enabled > > - CONFIG_CRYPTO_GCM: enabled > > - CONFIG_CRYPTO_SEQIV: enabled > > - CONFIG_CRYPTO_GHASH: enabled > > - CONFIG_XFRM: enabled > > - CONFIG_XFRM_USER: missing > > - CONFIG_XFRM_ALGO: missing > > - CONFIG_INET_ESP: missing > > - CONFIG_INET_XFRM_MODE_TRANSPORT: enabled > > - "mipvlan": > > - CONFIG_IPVLAN: missing > > - "macvlan": > > - CONFIG_MACVLAN: enabled (as module) > > - CONFIG_DUMMY: missing > > - "ftp,tftp client in container": > > - CONFIG_NF_NAT_FTP: missing > > - CONFIG_NF_CONNTRACK_FTP: missing > > - CONFIG_NF_NAT_TFTP: missing > > - CONFIG_NF_CONNTRACK_TFTP: missing > > - Storage Drivers: > > - "aufs": > > - CONFIG_AUFS_FS: missing > > - "btrfs": > > - CONFIG_BTRFS_FS: enabled (as module) > > - CONFIG_BTRFS_FS_POSIX_ACL: enabled > > - "devicemapper": > > - CONFIG_BLK_DEV_DM: missing > > - CONFIG_DM_THIN_PROVISIONING: missing > > - "overlay": > > - CONFIG_OVERLAY_FS: enabled (as module) > > - "zfs": > > - /dev/zfs: missing > > - zfs command: missing > > - zpool command: missing > > Limits: > > - /proc/sys/kernel/keys/root_maxkeys: 1000000 > > “docker –version” gives: > > Docker version 1.12.5, build 7392c3b > > From the config output, I see that some variables are not enabled. Could this be an issue? > > Kind regards, > > Russell > > > > Follow Us: LinkedIn | Twitter | Facebook > > Roke Manor Research Limited, Romsey, Hampshire, SO51 0ZN, United Kingdom. Part of the Chemring Group. Registered in England & Wales. Registered No: 00267550. The information contained in this e-mail and any attachments is proprietary to Roke Manor Research Limited and must not be passed to any third party without permission. This communication is for information only and shall not create or change any contractual relationship. > www.roke.co.uk<http://www.roke.co.uk> > > ________________________________ > -- > _______________________________________________ > meta-virtualization mailing list > meta-virtualization@yoctoproject.org > https://lists.yoctoproject.org/listinfo/meta-virtualization<https://lists.yoctoproject.org/listinfo/meta-virtualization> [-- Attachment #2: Type: text/html, Size: 24913 bytes --] ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2019-02-11 9:59 UTC | newest] Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2019-02-01 15:31 Adding Docker to NXP Image fails to execute run on target Coy, Russell 2019-02-07 15:03 ` Mark Asselstine 2019-02-11 9:59 ` Coy, Russell
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.