blub4747 Posted August 14, 2018 Posted August 14, 2018 Hello Community, I am trying to install Docker on my Cubietruck. As a guide i used the official guide by Docker https://docs.docker.com/install/linux/docker-ce/ubuntu/#upgrade-docker-ce When I am at actual installation step I walking in this following error msg. Does anyone have a idea where to start looking ? Thx.blub474 Quote lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.5 LTS Release: 16.04 Codename: xenial Quote Job for docker.service failed because the control process exited with error code. See "systemctl status docker.service" and "journalctl -xe" for details. invoke-rc.d: initscript docker, action "start" failed. ● docker.service - Docker Application Container Engine Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled) Active: activating (auto-restart) (Result: exit-code) since Tue 2018-08-14 13:13:00 UTC; 48ms ago Docs: https://docs.docker.com Process: 6705 ExecStart=/usr/bin/dockerd -H fd:// (code=exited, status=1/FAILURE) Main PID: 6705 (code=exited, status=1/FAILURE) Aug 14 13:13:00 cubietruck systemd[1]: Failed to start Docker Application Container Engine. Aug 14 13:13:00 cubietruck systemd[1]: docker.service: Unit entered failed state. Aug 14 13:13:00 cubietruck systemd[1]: docker.service: Failed with result 'exit-code'. dpkg: error processing package docker-ce (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: docker-ce E: Sub-process /usr/bin/dpkg returned an error code (1)
Igor Posted August 14, 2018 Posted August 14, 2018 1 hour ago, blub4747 said: Does anyone have a idea where to start looking ? You forget to supply the most important data. Not possible to help. Type: armbianmonitor -u
umiddelb Posted August 14, 2018 Posted August 14, 2018 Most likely the kernel you are using does not provide all the feature necessary to start docker. If you have access to the kernel configuration, you may check it by yourself, see here for details. As an alternative you may check the Ubuntu provided packages for Docker: sudo apt -y install lxc aufs-tools cgroup-lite apparmor docker.io
blub4747 Posted August 15, 2018 Author Posted August 15, 2018 Thank you for your replies. I just ran the the command by and the upload is accessible via http://ix.io/1keQ I also forgot to mention that Iam a slightly older kernel version. eg uname -a Linux cubietruck 3.4.113-sun7i #16 SMP PREEMPT Wed Jan 24 19:20:59 CET 2018 armv7l armv7l armv7l GNU/Linux Since this image also supports access to the nand memory. I also uploading the result of that curl script. Once again, thank you guys. I just tried the command for the docker packages by ubuntu. Here is the output. Quote Job for docker.service failed because the control process exited with error code. See "systemctl status docker.service" and "journalctl -xe" for details. invoke-rc.d: initscript docker, action "start" failed. ● docker.service - Docker Application Container Engine Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Wed 2018-08-15 06:34:32 UTC; 50ms ago Docs: https://docs.docker.com Process: 12672 ExecStart=/usr/bin/dockerd -H fd:// $DOCKER_OPTS (code=exited, status=1/FAILURE) Main PID: 12672 (code=exited, status=1/FAILURE) Memory: 8.0K CPU: 357ms CGroup: /system.slice/docker.service Aug 15 06:34:31 cubietruck systemd[1]: Starting Docker Application Container Engine... Aug 15 06:34:31 cubietruck dockerd[12672]: time="2018-08-15T06:34:31.803602365Z" level=info msg="libcontai...678" Aug 15 06:34:32 cubietruck dockerd[12672]: time="2018-08-15T06:34:32.820296447Z" level=fatal msg="Your Lin...er." Aug 15 06:34:32 cubietruck systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE Aug 15 06:34:32 cubietruck systemd[1]: Failed to start Docker Application Container Engine. Aug 15 06:34:32 cubietruck systemd[1]: docker.service: Unit entered failed state. Aug 15 06:34:32 cubietruck systemd[1]: docker.service: Failed with result 'exit-code'. Hint: Some lines were ellipsized, use -l to show in full. Quote curl -L https://raw.githubusercontent.com/docker/docker/master/contrib/check-config.sh | /bin/bash /dev/stdin /path/to/.config % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 10257 100 10257 0 0 10474 0 --:--:-- --:--:-- --:--:-- 10477 warning: /path/to/.config does not exist, searching other paths for kernel config ... 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: enabled - CONFIG_CGROUP_SCHED: enabled - CONFIG_CPUSETS: enabled - CONFIG_MEMCG: missing - CONFIG_KEYS: enabled - CONFIG_VETH: enabled (as module) - CONFIG_BRIDGE: enabled (as module) - CONFIG_BRIDGE_NETFILTER: enabled - CONFIG_NF_NAT_IPV4: missing - 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: enabled (as module) - CONFIG_IP_NF_NAT: missing - CONFIG_NF_NAT: enabled (as module) - CONFIG_NF_NAT_NEEDED: enabled - CONFIG_POSIX_MQUEUE: enabled - CONFIG_DEVPTS_MULTIPLE_INSTANCES: enabled Optional Features: - CONFIG_USER_NS: enabled - CONFIG_SECCOMP: missing - CONFIG_CGROUP_PIDS: missing - CONFIG_MEMCG_SWAP: missing - CONFIG_MEMCG_SWAP_ENABLED: missing (cgroup swap accounting is currently enabled) - CONFIG_MEMCG_KMEM: missing - CONFIG_RESOURCE_COUNTERS: enabled - CONFIG_BLK_CGROUP: enabled - CONFIG_BLK_DEV_THROTTLING: missing - CONFIG_IOSCHED_CFQ: enabled - CONFIG_CFQ_GROUP_IOSCHED: enabled - CONFIG_CGROUP_PERF: enabled - CONFIG_CGROUP_HUGETLB: missing - CONFIG_NET_CLS_CGROUP: enabled (as module) - CONFIG_NETPRIO_CGROUP: enabled (as module) - CONFIG_CFS_BANDWIDTH: enabled - CONFIG_FAIR_GROUP_SCHED: enabled - CONFIG_RT_GROUP_SCHED: enabled - CONFIG_IP_VS: enabled (as module) - CONFIG_IP_VS_NFCT: enabled - CONFIG_IP_VS_RR: enabled (as module) - CONFIG_EXT3_FS: enabled - CONFIG_EXT3_FS_XATTR: enabled - CONFIG_EXT3_FS_POSIX_ACL: enabled - CONFIG_EXT3_FS_SECURITY: enabled - CONFIG_EXT4_FS: enabled - CONFIG_EXT4_FS_POSIX_ACL: enabled - CONFIG_EXT4_FS_SECURITY: enabled - Network Drivers: - "overlay": - CONFIG_VXLAN: missing Optional (for encrypted networks): - CONFIG_CRYPTO: enabled - CONFIG_CRYPTO_AEAD: enabled - CONFIG_CRYPTO_GCM: enabled (as module) - CONFIG_CRYPTO_SEQIV: enabled - CONFIG_CRYPTO_GHASH: enabled (as module) - CONFIG_XFRM: enabled - CONFIG_XFRM_USER: enabled - CONFIG_XFRM_ALGO: missing - CONFIG_INET_ESP: enabled (as module) - CONFIG_INET_XFRM_MODE_TRANSPORT: enabled (as module) - "ipvlan": - CONFIG_IPVLAN: missing - "macvlan": - CONFIG_MACVLAN: enabled - CONFIG_DUMMY: missing - "ftp,tftp client in container": - CONFIG_NF_NAT_FTP: enabled (as module) - CONFIG_NF_CONNTRACK_FTP: enabled (as module) - CONFIG_NF_NAT_TFTP: enabled (as module) - CONFIG_NF_CONNTRACK_TFTP: enabled (as module) - Storage Drivers: - "aufs": - CONFIG_AUFS_FS: missing - "btrfs": - CONFIG_BTRFS_FS: enabled - CONFIG_BTRFS_FS_POSIX_ACL: missing - "devicemapper": - CONFIG_BLK_DEV_DM: enabled - CONFIG_DM_THIN_PROVISIONING: enabled (as module) - "overlay": - CONFIG_OVERLAY_FS: missing - "zfs": - /dev/zfs: missing - zfs command: missing - zpool command: missing Limits: - /proc/sys/kernel/keys/root_maxkeys: 1000000
blub4747 Posted August 15, 2018 Author Posted August 15, 2018 Hello community, I am currently using a armbian Image with a bit older kernel. 3.4.113-sun7i Since this Image is the only one which also allows me to use the nand memory on my cubietruck. I also went through all other images with a 4.14.14 kernel and none of them support that nand memory. I am therefore considering building my own image. However I don't know where to enable where in the built engine to enable support for nand memory. Can anybody please tell where in the built machine to look for a such a option ? Thank you, blub4747
Igor Posted August 15, 2018 Posted August 15, 2018 2 hours ago, blub4747 said: Linux cubietruck 3.4.113-sun7i Forget about. Docker needs a newer version. You need to move to NEXT 4.14.y kernel and it will work.
blub4747 Posted August 15, 2018 Author Posted August 15, 2018 Thank you for clearing this issue up. The main reason why i wanted to use this image is. is the fact that it supports the nand memory on my Cubietruck. Is there are a different image with a 4.14 kernel which also does support nand memory ?
Igor Posted August 15, 2018 Posted August 15, 2018 1 minute ago, blub4747 said: Thank you for clearing this issue up. The main reason why i wanted to use this image is. is the fact that it supports the nand memory on my Cubietruck. Is there are a different image with a 4.14 kernel which also does support nand memory ? No, there is no support for NAND in the modern kernel. AFAIK you can enable in armbian-config via overlay and access it, but you can't boot from it. Unfortunately, the problem you face is quite common - you have to make compromises. BTW. NAND is slower and less reliable than most modern SD cards.
martinayotte Posted August 15, 2018 Posted August 15, 2018 Unfortunately, NAND support on Mainline is completely different than the one on Legacy. On top of that, Mainline NAND support isn't working properly yet, lot of issues with bad sectors handling, etc. I doubt NAND support on Mainline will ever come rock solid ...
blub4747 Posted August 15, 2018 Author Posted August 15, 2018 once again Thank you for clarifying a lot issues. So I guess I will have forget about using that unstable NAND memory. Thx, blub4747
martinayotte Posted August 15, 2018 Posted August 15, 2018 Right ! All newer SoC boards are not using NAND anymore but eMMC instead ...
duong.dt7@gmail.com Posted August 16, 2018 Posted August 16, 2018 On 8/15/2018 at 3:54 PM, Igor said: root@vegas805:~# uname -a Linux vegas805 3.10.108 #5 SMP PREEMPT Fri Mar 30 09:42:01 MSK 2018 armv7l GNU/Linux I follow here https://github.com/hypriot/arm-compose and error code Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-build-GY7XWm/dockerpty/ how to update firmware for s805 to kernel 4.14? thanks On 8/15/2018 at 3:54 PM, Igor said: On 8/15/2018 at 3:54 PM, Igor said: Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-build-GY7XWm/dockerpty/ Forget about. Docker needs a newer version. You need to move to NEXT 4.14.y kernel and it will work.
Igor Posted August 17, 2018 Posted August 17, 2018 10 hours ago, duong.dt7@gmail.com said: how to update firmware for s805 to kernel 4.14? You can't. There is only very limited support for s805 and we don't support it. Check Odroid C1 NEXT, that's the best what is possible on this chip and modern kernel. Ethernet works, 4 cores are UP, memory is recognized, USB works, ... but there is no eMMC support, no HDMI, ...
duong.dt7@gmail.com Posted August 17, 2018 Posted August 17, 2018 3 hours ago, Igor said: You can't. There is only very limited support for s805 and we don't support it. Check Odroid C1 NEXT, that's the best what is possible on this chip and modern kernel. Ethernet works, 4 cores are UP, memory is recognized, USB works, ... but there is no eMMC support, no HDMI, ... thank for reply i want use it for IOT, not need HDMI i try https://www.armbian.com/odroid-c1/ but not run how to intall rom odroid-c1 for mxq s805?
Igor Posted August 17, 2018 Posted August 17, 2018 38 minutes ago, duong.dt7@gmail.com said: how to intall rom odroid-c1 for mxq s805? I don't know. In theory: you need to use original u-boot and load this modern kernel. I am just saying modern kernel exists and it works for this chip. But you need to adopt/create DT board configuration from exiting kernel ... if you don't know what I am talking about, forget about. Or start exploring.
Recommended Posts