Now that seccomp support is compiled into the kernel you can use the official docker builds located at https://download.docker.com/linux/static/stable/armhf/docker-19.03.8.tgz. I would recommend this particular build as docker-19.03.9 and above seem to have a dockerd binary that is not compatible with the EX4100 at least. Copy the extracted files from the tgz above into /mnt/HD/HD_a2/Nas_Prog/docker/docker if you are using the third party docker install for WD NAS that is floating around.
This is the first build where seccomp has been available on arm so into new territory on this one. I’ve only got as far as installing portainer on my Ex4100 so not ran into the issue.
Someone suggested they fixed it in that link by updating to 19.03.12 but any versions above 19.03.08 seem to not have a working dockerd binary (at least for me), but could be worth trying in any case and see if you have better luck.
Strangely on my end, after swapping the files on the destination docker stops working.
I start the application and then try to log to navigate it through port 9000 and get connection refused, it only starts working again after reinstalling the application. Did any of you guys had this problem?
I had to manually restart portainer to get it work.
In your output the container seems to be created 13 days ago, but not running.
docker rm pedantic_golick
And start a new portainer instance by:
I see some error messages in the output, but the container starts up successfully and port 9000 is available:
# sh /shares/Volume_1/Nas_Prog/docker/update_portainer.sh
/shares/Volume_1/Nas_Prog/docker/update_portainer.sh: line 1: !#/bin/sh: not found
Error response from daemon: No such container: portainer
Error: No such container: portainer
Using default tag: latest
latest: Pulling from portainer/portainer
Status: Image is up to date for portainer/portainer:latest
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
4cf60f58beca portainer/portainer "/portainer" 3 seconds ago Up Less than a second 0.0.0.0:9000->9000/tcp portainer