Bullseye missing portainer?


NeoFax
 Share

1 1

Recommended Posts

I have docker running on a OrangePi Zero2, but it seems portainer is having problems.  Here is the error I get:

 

Quote

sudo docker run -d -p 8000:8000 -p 9443:9443 --name portainer --restart=always -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer-ce:2.11.1
Unable to find image 'portainer/portainer-ce:2.11.1' locally
2.11.1: Pulling from portainer/portainer-ce
772227786281: Pull complete 
96fd13befc87: Pull complete 
8f4350c9e38e: Pull complete 
Digest: sha256:3ff080a0cd2a45bd0bde046069973b3fe642c3e4d43c5b429dd7b77f0057c7d7
Status: Downloaded newer image for portainer/portainer-ce:2.11.1
3cfd5616708777020d239014c1f690a164f737ff718675a70862efab3d684eea
docker: Error response from daemon: failed to create shim: OCI runtime create failed: container_linux.go:380: starting container process caused: process_linux.go:545: container init caused: process_linux.go:508: setting cgroup config for procHooks process caused: bpf_prog_query(BPF_CGROUP_DEVICE) failed: invalid argument: unknown.
terry@orangepizero2:~$ sudo docker ps
CONTAINER ID   IMAGE     COMMAND   CREATED   STATUS    PORTS     NAMES
terry@orangepizero2:~$ 
 

 

 

Edited by NeoFax
Link to post
Share on other sites

Armbian is a community driven open source project. Do you like to contribute your code?

OK, well the solution is that the kernel needs the cgroup.freeze feature which is only in kernels above 4.15.  Which I am running Linux 4.9.255-sun50iw9 aarch64.  I am going to try and see if one of the other newer builds will boot and go from there tomorrow.

Link to post
Share on other sites

Interesting I failed to get hello-world docker running relating to cgroupsV2 issues similarly referenced

 

https://my-take-on.tech/2021/05/07/fix-docker-cgroup-errors-after-systemd-248-update/

 

Making the suggested changes to OrangePi Zero2 bullseye  armbianEnv.txt and recompiling boot.cmd and boot.scr has not worked, but I might be missing something as this was done in haste.

Link to post
Share on other sites

So-far no luck getting a working docker running on OrangePiZero2 

 

gordon@orangepizero2:~$ uname -a
Linux orangepizero2 4.9.255-sun50iw9 #1 SMP PREEMPT Tue Mar 1 23:28:34 UTC 2022 aarch64 GNU/Linux
gordon@orangepizero2:~$ docker run -d --name=Portainer --hostname=Portainer --network=host --restart=always -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data -e TZ='Africa/Johannesburg' portainer/portainer-ce:2.11.1
Unable to find image 'portainer/portainer-ce:2.11.1' locally
2.11.1: Pulling from portainer/portainer-ce
772227786281: Pull complete 
96fd13befc87: Pull complete 
8f4350c9e38e: Pull complete 
Digest: sha256:3ff080a0cd2a45bd0bde046069973b3fe642c3e4d43c5b429dd7b77f0057c7d7
Status: Downloaded newer image for portainer/portainer-ce:2.11.1
d0ece38e32ffd8dafd560eb09e2584a27e82162b43b579f7db29954944f3df69
docker: Error response from daemon: failed to create shim: OCI runtime create failed: container_linux.go:380: starting container process caused: process_linux.go:545: container init caused: process_linux.go:508: setting cgroup config for procHooks process caused: bpf_prog_query(BPF_CGROUP_DEVICE) failed: invalid argument: unknown.
gordon@orangepizero2:~$ zcat /proc/config.gz   | grep -E 'CONFIG_BPF|CONFIG_FREEZER'
CONFIG_BPF=y
CONFIG_BPF_SYSCALL=y
CONFIG_FREEZER=y
# CONFIG_BPF_JIT is not set
gordon@orangepizero2:~$ 

 

The hack-able solution I've read is to downgrade to cgroups v1 and set with kernel parameter  systemd.unified_cgroup_hierarchy=0

 

Otherwise as noted you need kernel 4.15 as minimum for use with cgroups v2

 

@NeoFax I had first changed to Debian nftables for the service, nonetheless was curious how you got any containers running in the first place, as I immediately hit the problem with hello-world.

 

Anyway will try to figure out and post if workable solution happens.

Edited by ALIGMSTEN
clarification
Link to post
Share on other sites

I downloaded the new image from the OrangePi website for this board.  It works good, but it may never be updated as the vendor is not very good at supporting it.  As the kernel developers work more on these style of boards, it will float downstream into Armbian.  The best advice I can give is help out here in Armbian the best you can and it may work in the future.

Link to post
Share on other sites

Ok thank you @NeoFaxmuch appreciate that, yes intending to help here.

 

It seems changes to boot.scr and boot.cmd not possible

 

Notes here: https://github.com/armbian/build/pull/2620 

 

hexdump0815 comments: the u-boot ignores the kernel cmdline you give it via boot.scr or extlinux.conf and always uses the bootargs given in the dtb (built into u-boot)

 

hexdump0815: notes and ugly hacks can be found here: https://github.com/hexdump0815/u-boot-misc/blob/master/readme.h616-legacy and here: https://github.com/hexdump0815/u-boot-misc/tree/master/misc.h616-legacy

Link to post
Share on other sites

However, tomorrow I will start working on making a 22.05 build for OPIZero2 with a new 5.15.25 kernel, which should be able to run docker on it.  I just created a new Bullseye build for my OPI3-LTS board and docker is working on it.  Where as before I had to use the image from the OrangePi website to get it to even boot.

Link to post
Share on other sites

Unfortunately first try at this no good, image doesn't boot, no green light, can't ssh, red light permanent, serial output attached.

 

Had quite a few issues get the build environment to run which i had worked through.

 

1: jq: error (at <stdin>1:): Cannot iterate over null (null)

2: debootstrap-ng was interrupted

 

The compiled build: sudo ./compile.sh EXPERT="yes" NO_APT_CACHER="yes"

 

More than likely rookie errors, will have to go through logs and do some more reading.

armbianboot20220430_bullseye_edge_5.17.5_minimal.txt

Link to post
Share on other sites

Correction can ssh into board, however armbian-config total 0 nothing found...

 

root@orangepizero2:~# root@orangepizero2:~# df -Th
Filesystem     Type      Size  Used Avail Use% Mounted on
udev           devtmpfs  423M     0  423M   0% /dev
tmpfs          tmpfs      99M  440K   99M   1% /run
/dev/mmcblk0p1 ext4       29G  887M   28G   4% /
tmpfs          tmpfs     493M     0  493M   0% /dev/shm
tmpfs          tmpfs     5.0M     0  5.0M   0% /run/lock
tmpfs          tmpfs     493M     0  493M   0% /tmp
/dev/zram1     ext4       49M  5.9M   39M  14% /var/log
tmpfs          tmpfs      99M     0   99M   0% /run/user/0
root@orangepizero2:~# df -Th | grep "^/dev"
/dev/mmcblk0p1 ext4       29G  887M   28G   4% /
/dev/zram1     ext4       49M  5.9M   39M  14% /var/log
root@orangepizero2:~#

Link to post
Share on other sites

CONFUSED TO SAY THE LEAST! NO GREEN LIGHT???

 

 

login as: gordon
gordon@10.0.0.19's password:
  ___  ____  _   _____             ____
 / _ \|  _ \(_) |__  /___ _ __ ___|___ \
| | | | |_) | |   / // _ \ '__/ _ \ __) |
| |_| |  __/| |  / /|  __/ | | (_) / __/
 \___/|_|   |_| /____\___|_|  \___/_____|

Welcome to Armbian 22.05.0-trunk Bullseye with bleeding edge Linux 5.16.18-sunxi64

No end-user support: built from trunk

System load:   3%               Up time:       1 min
Memory usage:  9% of 984M       IP:            10.0.0.19
CPU temp:      46°C             Usage of /:    7% of 30G

[ General system configuration (beta): armbian-config ]

gordon@orangepizero2:~$
 

Link to post
Share on other sites

At this point I am assuming it will be needed to apply the userpatches by building again.

 

gordon@orangepizero2:~$ sudo armbianmonitor -m
[sudo] password for gordon:
Stop monitoring using [ctrl]-[c]
Time      CPU n/a    load %cpu %sys %usr %nice %io %irq   CPU

11:18:08:   ---      0.08   0%   0%   0%   0%   0%   0% 46.2°C
11:18:13:   ---      0.07   0%   0%   0%   0%   0%   0% 47.2°C
11:18:18:   ---      0.07   0%   0%   0%   0%   0%   0% 46.4°C
11:18:23:   ---      0.06   0%   0%   0%   0%   0%   0% 45.9°C
11:18:28:   ---      0.06   0%   0%   0%   0%   0%   0% 46.6°C
11:18:33:   ---      0.05   0%   0%   0%   0%   0%   0% 46.8°C
11:18:38:   ---      0.05   0%   0%   0%   0%   0%   0% 47.0°C
11:18:43:   ---      0.04   0%   0%   0%   0%   0%   0% 46.3°C^C

gordon@orangepizero2:~$

 

So far will chalk it up as a good bit of learning ...........

Link to post
Share on other sites

1 hour ago, ALIGMSTEN said:

Unfortunately first try at this no good, image doesn't boot, no green light, can't ssh, red light permanent, serial output attached.


Don't expect everything to work. That is close to mission impossible in this world. Armbian maintainers generate huge loss by dealing with their "customers", so this is not a problem of Armbian in any way.

 

https://docs.armbian.com/User-Guide_FAQ/#why-does-hardware-feature-xy-work-in-old-kernel-but-not-in-more-recent-one

This might shed some light. Support on modern kernel is written / ported basically from scratch and its mainly maintained by amateurs. Until they find fun / need in that. 
 

18 minutes ago, ALIGMSTEN said:

Welcome to Armbian 22.05.0-trunk Bullseye with bleeding edge Linux 5.16.18-sunxi64


You build and boot image from sources that works is already a nice success. A lot of work is needed in the backstage that this looks so simple.

Link to post
Share on other sites

Good day can confirm that Armbian 22.05.0-trunk Bullseye with bleeding edge Linux 5.16.18-sunxi64 Docker installs without any adjustments and Portainer installed and functioning. Usual caveats and warnings about such builds!docker-portainer-Armbian-22_05.0-trunk-Bullseye-with-bleeding-edge-Linux-5.jpg.93f388e93bc4c601e0d8507e1fdae546.jpg

Link to post
Share on other sites

I can confirm this as well.  I have been using it since Friday.  I am planning to rebuild with btrfs support as I just did that with my OrangePi3-LTS and it is working really well, but I use that as a desktop PC.

Link to post
Share on other sites

The only further insight I can add is that in my case the installations were from a terminal. The Armbian configure utility simple returned to the preceding prompt with zero further action. I did not have a deeper look into this other than an extremely quick squiz at the sources which looked right.

 

Perhaps while the Good Gentlemen at Armbian have fresh sight of this, I can point a 'missing' 'm' in the FAQ documentation Igor referenced above.

 

https://docs.armbian.com/User-Guide_FAQ/#why-does-armbian-not-support-tv-boxes-the-market-is-huge

Second paragraph first line: correction for documentation

However, in vast majority of cases, TV boxes are lacking any docuentation

However, in vast majority of cases, TV boxes are lacking any docu 'm' entation documentation

 

Have a nice evening!

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

1 1