umiddelb / armhf Goto Github PK

I get the following error on a Raspberry Pi Zero running Raspbian Stretch in part 4 of the instructions from this page:

curl -sSL http://downloads.hypriot.com/docker-hypriot_1.8.2-1_armhf.deb >/tmp/docker-hypriot_1.8.2-1_armhf.deb curl: (6) Could not resolve host: downloads.hypriot.com

@umiddelb, nothing directly related to your work here but thought you might have a clue :)

I was compiling a docker container on my C1 and it went offline... It still boots now (thankfully) but gives bus error. Using my Mac... it doesn't seem to repair/resolve the SD card.

Any clue or formatting is my best bet?

Thanks!

Hey @umiddelb, wondering if you found an easier way to build docker binaries for arm? :)

Hey @umiddelb,

great work for the documentation! Really interesting and helps me figure out what went wrong for my image.

I have a question if you can help me along:

1.) I did not compile my own kernel (so no aufs)
2.) Using a Odroid-C1 minimal from http://odroid.com/dokuwiki/doku.php?id=en:c1_ubuntu_minimal

I have a few errors like CONFIG_CGROUP_CPUACCT: missing in my attempt to fire up a container with your armhf image. (checked using the https://github.com/docker/docker/blob/master/contrib/check-config.sh)

Did you experience something similar on the C1 or is there something that i have overlooked?

3.) I used the binary for the 1.5.0 docker version you compiled

Thanks!!

Hey @umiddelb,

i also tried out the latest Ubuntu from Hardkernel and i ran the Docker check just to be sure.

Seems like by default, they did not enable the - cgroup hierarchy: nonexistent??

There's a script to do so as mentioned: https://github.com/tianon/cgroupfs-mount

So i thought i would mention to you in case someone asked the same thing. I will test out Docker 1.5.0 and see how it goes and report back.

Thanks!

The statement (https://github.com/umiddelb/armhf/wiki/Installing,-running,-using-docker-on-armhf-(ARMv7)-devices) that odroid stock kernel support AUFS is not correct any more. I upgrade my u2 to xu4 with stock kernel. When reusing root file system with docker container there, I found that default kernel config in xu4 doesn't support AUFS any more. Please update your statement.

Hi,
in https://github.com/umiddelb/armhf/wiki/Get-more-out-of-%22Das-U-Boot%22 I see you mention u-boot 2015 version for the Odroid C1. Do you know where these sources are?

Thank you

Just want to know, while building the custom Android kernel (arm64 architecture), is it possible to install corresponding Linux-headers with that.

As I want to install a few drivers software on Android and they are finding the Linux-headers corresponding to the android-kernel version? Can anyone please tell me how to do that?

I'm trying to build it on my own.

$ ./build --arm 6 1.9.0
...
Fetched 2527 kB in 1min 3s (40.1 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
E: Unable to locate package ubuntu-zfs
The command '/bin/sh -c apt-get update && apt-get install -y    apparmor        aufs-tools      automake        bash-completion    btrfs-tools     build-essential         createrepo      curl    dpkg-sig        git     iptables        libapparmor-dev    libcap-dev      libsqlite3-dev  mercurial       parallel        python-mock     python-pip      python-websocket  reprepro         ruby1.9.1       ruby1.9.1-dev   s3cmd=1.1.0*    ubuntu-zfs      libzfs-dev      --no-install-recommends' returned a non-zero code: 100
Makefile:74: recipe for target 'build' failed
make: *** [build] Error 1

I found there is no ubuntu-zfs_8~trusty_armhf.deb in PPA.
I don't know how to solve it. Please help. Thanks!

Uli, still compiling 1.7.1 but initially I tried building 1.8.1 and received the following error...

$ git clone -b 'v1.8.1' --single-branch https://github.com/docker/docker.git

$ sudo make build

...
Step 14 : RUN curl -sSL ...
2015/08/25 16:17:23 finalize namespace drop capabilities operation not permitted
2015/08/25 18:17:23 The command [/bin/sh -c curl -sSL https://golang.org/dl/go${GO_VERSION}.src.tar.gz | tar -v -C /usr/local -xz && mkdir -p /go/bin] returned a non-zero code: 1

make: *** [build] Error 1

Actually 1.7.1 build just failed as well. Similar problem but at a different step.

Removing intermediate container 89c1d0ca770d
Step 40 : ENV TOMLV_COMMIT 9baf8a8a9f2ed20a8e54160840c492f937eeaf9a
---> Running in 6974271ca401
---> d9662cb19f3c
Removing intermediate container 6974271ca401
Step 41 : RUN set -x && git clone https://github.com/BurntSushi/toml.git /go/src/github.com/BurntSushi/toml && (cd /go/src/github.com/BurntSushi/toml && git checkout -q $TOMLV_COMMIT)
---> Running in db87fab2b11a
2015/08/25 17:32:19 finalize namespace drop capabilities operation not permitted
2015/08/25 19:32:20 The command [/bin/sh -c set -x && git clone https://github.com/BurntSushi/toml.git /go/src/github.com/BurntSushi/toml && (cd /go/src/github.com/BurntSushi/toml && git checkout -q $TOMLV_COMMIT)] returned a non-zero code: 1
make: *** [build] Error 1

Just curious if you have seen the same and/or know how to get past this error.

Hello!

Regarding the

umiddelb/armhf/wiki/How-To-compile-a-custom-Linux-kernel-for-your-ARM-device

I wonder how does it work without ever specifying ARCH=arm in any make invocation, or ever mentioning it at all?

I doubt the tutorial expects the kernel is being built on some ARM host, so the host is likely x86, and we are building cross.

In this case, in particular, the recipe:

cd linux
make <default_config>
less .config

will try to find <devault_config> in arch/x86 rather than in arch/arm, and should fail.

If ARCH=arm should be set in the environment, it should better be explicitly stated in the tutorial, I think.

What do I miss?

I used to be able to build docker on my targets using the normal steps:

$ git clone -b 'v1.9.1' --single-branch https://github.com/docker/docker.git
$ cd docker
$ curl -L https://github.com/umiddelb/armhf/raw/master/Dockerfile.armv7 > Dockerfile
$ sudo make build
$ sudo make binary
Now, I get a make error ...at STEP 41:

go get -v -d github.com/cpuguy83/go-md2man package code.google.com/p/go.net/html: unable to detect version control system for code.google.com/ path
This kills the make. Is this a known issue?

Hi @terryburton,

you may switch to this imx linux kernel for the Utilite Pro and the CuBox-i, which is supposed to have better support. I will abandon linux-imx6-3.14.

Thank you very much for the nice tutorial https://github.com/umiddelb/armhf/wiki/Get-Docker-up-and-running-on-the-RaspberryPi-%28ARMv6%29-in-three-steps but there is one error for sudo sh run-builder.sh:

HEAD is now at c3959b1... Merge pull request #20526 from tiborvass/1.10.2-cherrypicks
# WARNING! I don't seem to be running in the Docker container.
# The result of this command might be an incorrect build, and will not be
#   officially supported.
#
# Try this instead: make all
# 

So in the end: How does it work when you want to build docker for ARM for the first time but you need a docker container for this to do this? So for the beginning I have to use a pre compiled docker package?

Hey @umiddelb,

Thank you for the great Wikipage :-)
I am a kernel compilation newbie and I would like to compile the mainline kernel with a realtime patch for the Odroid XU4. I found out that the newest Kernelversion.Patchlevel.Subslevel is 4.6.0.
I searched for the corresponding rt-patch and found
https://www.kernel.org/pub/linux/kernel/projects/rt/4.6/older/patch-4.6-rc7-rt1.patch.gz
Applying the patch with
zcat patch-4.6-rc7-rt1.patch.gz | patch -p1
results in a lot of patching errors. Is this the right way and the kernel is modifyied such that it is not possible to apply the patch or did I made some mistakes?

Greetings from Ilmenau (Germany),
Fabian

$ make imx_v7_cbi_hb_defconfig does not succeed... -->

*** Can't find default configuration "arch/x86/configs/imx_v7_cbi_hb_defconfig"!

Any idea where to go with this make configuration update?

Hey @umiddelb, i downloaded the image from your website for Cubox-i (actually running on hummingboard) but the .bz2 file gave me a .tar which uncompressed to the files for the SD.

Is that the right way to install by copying the files over to the SD? How do we expand and use the entire diskspace then? Thanks!

Hi @umiddelb , thanks for your docker binary file. It help me to build ARMv7 Raspberry Pi 2 version of weave, https://github.com/philipz/weave . But when build Raspberry Pi ARMv6 Arch. need ARMv6 docker binary static-link file, like https://github.com/umiddelb/armhf/blob/master/bin/arm7/docker-1.5.0 . Would you provide ARMv6 binany file? Or provide build steps document. Thank you!

Hey @umiddelb ,

can you advice on how you update your devices with a new docker version each time you build a new one?

Thanks! :)

@ewalbridge
Thank you for proofreading!

Hallo @tobiasjakobi ,

Vielen Dank fürs Ergänzen / Korrigieren!

Viele Grüße nach Bielefeld! (Ich bin vor 20 Jahren für meinen ersten Job an der Uni nach Bielefeld gezogen)

I'm using Docker under Buildroot at the moment (cross compiling docker, aufs, etc). Might be interesting to mention it.

Docker hasn't been merged yet but probably will be in the coming weeks.

See http://github.com/paralin/buildroot

All the steps work until this one:

( cd /mnt; sudo find * | sudo cpio -dump .../rootfs )

I get many messages of the form:

cpio: cannot make directory `...': Read-only file system

I'm also curious why you have three dots in a row instead of two.

You made a typo under the Odroid-C2 build instructions on this page: https://github.com/umiddelb/armhf/wiki/How-To-compile-a-custom-Linux-kernel-for-your-ARM-device - namely:

$ sudo cp arch/arm/boot/Image arch/arm/boot/dts/meson64_odroidc2.dtb /media/boot

should be

$ sudo cp arch/arm64/boot/Image arch/arm64/boot/dts/meson64_odroidc2.dtb /media/boot

Thanks for all your work!

I'm getting the following error when running STEP 5 of the build.sh:

curl: (56) SSL read: error:00000000:lib(0):func(0):reason(0), errno 104

gzip: stdin: unexpected end of file
tar: Unexpected EOF in archive
tar: Unexpected EOF in archive
tar: Error is not recoverable: exiting now
The command '/bin/sh -c curl -sSL https://github.com/hypriot/golang-armbuilds/releases/download/v${GO_VERSION}/go${GO_VERSION}.linux-armv7.tar.gz | tar -xz -C /usr/local' returned a non-zero code: 2

I'm running it using on a Raspberry Pi Zero.

Any ideas?

Thanks,
Carlos.

@chris-kobrzak @ubergesundheit @rjbrown99 @hakandilek @djmaze @rickyzhang82 @DylanSchell @kevincaradant @ynk @RicJac @juliancheal @cawa0505 @chrisspen @lexruee @ManfredHerrmann @oldgregg @daozhao @MaksymBilenko @sjuut @kennethlimcp @ewalbridge @docdawning @siliond @steveej @The-Loeki @jefby @flosky @jgjl @CodeWire @jforge @stuart-c

Dear Stargazers et al.,

I'm currently trying to get basic docker support enabled into the standard raspbian linux kernel. If you want to support this attempt, please leave a comment here
...
"I'd also like to know how many users actually want this feature, so if you do then post here."

Hi, could you update your XU4 example with the 4.14 branch from Hardkernel instead of 4.9?
It needs a branch change and also you can make odroidxu4_defconfig instead of xu3_defconfig.

Thanks!

I'm looking for debian base images to build armhf container images and I've really liked your work. However, I notice that you have not updated this repo and the images on dockerhub in a while. Have you abandoned or paused this effort, and if so, which base images would you recommend to use instead? (I'm using odroids and am not interested in raspian base images.) Thanks much!!

I would like to have this patch applied by default to the ioft master branch. Is this realistic?

Hello

I need some assistance on an issue that I am facing. I followed your instructions and to me it looks like it is working. Please see this record.

Now I try to run a container called Collabora. I used this command:
docker run -t -d -p 9980:9980 -e "domain=sub\.domain\.com" --cap-add MKNOD collabora/code

but it fails. Here is the error log.

Any idea how to get this fixed? Or just a hint where I can start to investigate? Is this might be an collabora container issue?

Your assistance is highly appreciated.

Kind regards
//nephilim

Thanks for the wiki postings. Very helpful. I'm running a UX4. Any thoughts on the bad CRC message?

odroid@odroid:~$ uname -a
Linux odroid 3.10.92-76 #1 SMP PREEMPT Tue Jan 12 16:55:48 BRST 2016 armv7l armv7l armv7l GNU/Linux

odroid@odroid:~$ cat /etc/fw_env.config
# <device>   <offset> <length>
/dev/mmcblk0 0x99E00   0x4000
odroid@odroid:~$

odroid@odroid:~$ fw_printenv
Warning: Bad CRC, using default environment
bootargs=
bootcmd=bootp; setenv bootargs root=/dev/nfs nfsroot=${serverip}:${rootpath} ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}::off; bootm
bootdelay=3
baudrate=115200
stdin=serial,cros-ec-keyb
stdout=serial,lcd
stderr=serial,lcd

In regards to https://github.com/umiddelb/armhf/wiki/Get-more-out-of-%22Das-U-Boot%22

Please read http://git.denx.de/?p=u-boot.git;a=blob;f=doc/README.distro;h=3715c8c3bad7339c41a9da7e1f11fd6d4f902a08;hb=HEAD there is a defined way to setup u-boot to ensure that distros can simply support hardware. The instructions you have are not at all close to meeting the specification.