I want to set up a cluster of edge-computing, therefore, I need to install the flink on the raspberry-pi.
I am using the raspberry 4b and the system is raspbian. Version is:
Distributor ID: Raspbian
Description: Raspbian GNU/Linux 10 (buster)
Release: 10
Codename: buster
When I just type the docker pull flink, there is an error called:
ERROR: no matching manifest for linux/arm/v7 in the manifest list entries
How could I install it correctly? Thanks a lot!
I also had the same problem, and then searched for an ARMv7 compatible image and found this tag: 1.8-scala_2.12-alpine. It is a few versions behind, but works on my k3s cluster on raspberry pi.
Related
I have installed Processor-SDK-AM57x on Ubuntu 18.04 linux distribution and build my project successfully.
I have to create build environment on Docker image and build my application inside contianer.
how can I install my dependencies Processor-SDK-AM57x on Ubuntu 18.04.
do I need to include a texas instruments key into the trusted keys of you Docker-Container, if yes how?
any help in this regard would be appriciated!
Thanks
I have a local setup of three raspberry pi's and followed the tutorial on here.
I managed to get my microk8s cluster running. Next I wanted to deploy Jenkins.
Whenever I execute the first command:
kubectl create -f jenkins-deployment.yaml -n jenkins
I get the following error:
standard_init_linux.go:219: exec user process caused: exec format error
Some other searches suggest installing docker. However in the tutorial there is nothing about installing docker. Any ideas what is happening here?
Docker vs. containerd
Regarding your suggestion about the docker.
From Version 1.14.0 of MicroK8s (released 25 March 2019) containerd replaced dockerd.
Starting from version 1.14.0 containerd automatically ships with MicroK8S installation So, you don't need dockerd as CRI.
Below you can find modules MicroK8S set up during installation:
The following systemd services will be running in your system:
snap.microk8s.daemon-apiserver, is the kube-apiserver daemon started using the arguments in ${SNAP_DATA}/args/kube-apiserver
snap.microk8s.daemon-controller-manager, is the kube-controller-manager daemon started using the arguments in ${SNAP_DATA}/args/kube-controller-manager
snap.microk8s.daemon-scheduler, is the kube-scheduler daemon started using the arguments in ${SNAP_DATA}/args/kube-scheduler
snap.microk8s.daemon-kubelet, is the kubelet daemon started using the arguments in ${SNAP_DATA}/args/kubelet
snap.microk8s.daemon-proxy, is the kube-proxy daemon started using the arguments in ${SNAP_DATA}/args/kube-proxy
snap.microk8s.daemon-containerd, is the containerd daemon started using the configuration in ${SNAP_DATA}/args/containerd and ${SNAP_DATA}/args/containerd-template.toml.
snap.microk8s.daemon-etcd, is the etcd daemon started using the arguments in ${SNAP_DATA}/args/etcd
ARM architecture
Next, Raspberry Pi and, as mentioned previously by community, ARM.
You can not use regular amd64-based images for ARM architecture.
Possible solutions
To solve a problem, I recommend you 2 options below.
Use already prepared ARM-based image of Jenkins for ARM architecture. Also you can search images for Raspberry Pi with filters. Just select which architecture you would like to use: ARM, ARM64, etc.
Some images have been ported for other architectures, and many of these are officially supported (to various degrees).
ARMv6 32-bit (arm32v6): https://hub.docker.com/u/arm32v6/
ARMv7 32-bit (arm32v7): https://hub.docker.com/u/arm32v7/
ARMv8 64-bit (arm64v8): https://hub.docker.com/u/arm64v8/
Prepare your own image for ARM using buildx
References:
Multi-arch build and images, the simple way
Cross building ARM images on Docker Desktop
This was a huge surprise for me:
Today, using Docker For Mac (18.03.1-ce-mac65), I ran a Debian Stretch image. Inside the image I mounted the latest Raspbian Stretch image (2018-04-18-raspbian-stretch-lite) using mount. I then used chroot to this mounted Raspbian filesystem.
This is where it got weird. I was able to use apt (without any special modifications) to install software into this mounted filesystem.
Running:
dpkg --print-architecture
returned: armfh
and the software I installed (vim) worked like a charm
I was even able to compile a simple program using gcc and run it.
But, I need to know! How is this possible?
According to Docker:
Docker for Mac provides binfmt_misc multi architecture support, so you can run containers for different Linux architectures, such as arm, mips, ppc64le, and even s390x.
EDIT
On Linux, you can install qemu-user-static and then follow this git repo to get cross-architecture support!
I am having the following warning message when issueing docker commands: (ex: docker ps)
C:\Users\whha>docker ps
time="2017-01-24T23:17:36+01:00" level=warning msg="Unable to use system certificate pool: crypto/x509: system root pool is not available on Windows"
Any idea how can it be avoided?
I´m running docker using docker toolbox on windows 8.1.
Installing the last available version solved the problem for me (https://github.com/docker/toolbox/releases) :
BEFORE
minux#DESKTOP-OCQQ65T MINGW64 /c
$ docker --version
time="2017-04-05T17:56:55+02:00" level=info msg="Unable to use system
certificate pool: crypto/x509: system root pool is not available on Windows"
Docker version 17.03.1-ce, build c6d412e
AFTER
minux#DESKTOP-OCQQ65T MINGW64 /c
$ docker --version
Docker version 17.04.0-ce-rc2, build 2f35d73
I started having this problem today after updating to the docker toolbox version 1.13.1 of Docker Toolbox for windows.
Checking around the internet, and saw a github issue that this problem can't be fixed for windows.
https://github.com/docker/for-win/issues/422
Hence, probably has to follow #mayur_patil's suggestion to roll back to 1.12.x version. FYI, previous release can be found here: https://github.com/docker/toolbox/releases
I have installed docker toolbox version 1.13.1 for windows.
OS : Windows 10 Enterprise.
I solved the same issue with the v 1.12.6 instead 1.13.x.
You can change version series.
I was getting this error on Docker-toolbox 1.13.1
After that I downgraded to 1.12.2 and my problem solved.
OS: Windows 7 SP1
Check out and reply.
Had the same problem and solved it by download v1.12.6 from:
https://github.com/docker/toolbox/releases
I want to install docker 1.3.1 on my centos 6.5 environment but I have no idea how to find it in the epel. I'm quite new to docker. Can anyone help me out? Thanks
Clearly stated in the Docker documentation:
Docker runs on CentOS 7.X.
CentOS 6.5 is not CentOS 7.X. Docker is not available for your old operating system.
Furthermore, you didn't give any details about your computer, but you should remain aware that Docker only works on 64-bit systems.
By the way, you should take better care of your computer; in CentOS, the minor version number is updated automatically by the package manager. So the fact that you are two versions behind (CentOS 6 is currently on 6.7) indicates that you are not performing updates to your packages, and could have various security vulnerabilities. You should update your system regularly, by simply running yum update.