seccomp: config provided but seccomp not supported

[ajhorvath20]

trafficstars

Hi, I have this version running on My Cloud EX2 Ultra

root@Pandora-Box ~ # docker version
Client: Docker Engine - Community
 Version:           19.03.8
 API version:       1.40
 Go version:        go1.12.17
 Git commit:        
 Built:             Thu Mar 12 10:31:28 2020
 OS/Arch:           linux/arm
 Experimental:      false

And thats the output I am getting

root@Pandora-Box ~ # docker run -d -p 9000:9000 --name=portainer --restart=always -v /var/run/docker.sock:/var/run/docker.sock -v /shares/Docker/portainer:/data portainer/portainer-ce
766967c69216cf917ef04e2d73266c9f224c079410ffbb988a18ea778aed0126
docker: Error response from daemon: OCI runtime create failed: container_linux.go:349: starting container process caused "seccomp: config provided but seccomp not supported": unknown.
ERRO[0009] error waiting for container: context canceled 

root@Pandora-Box ~ # docker ps
CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS              PORTS               NAMES
root@Pandora-Box ~ # docker ps -a
CONTAINER ID        IMAGE                    COMMAND             CREATED             STATUS              PORTS                              NAMES
766967c69216        portainer/portainer-ce   "/portainer"        8 minutes ago       Created             8000/tcp, 0.0.0.0:9000->9000/tcp   portainer

Need little help to fix the issue.

Thanks

[JediNite]

Hi

Seccomp was not supported with the kernel in OS3, but is in the newer releases. Suggest upgrading your docket to a newer release.

JediNite

Get Outlook for iOShttps://aka.ms/o0ukef

---

From: ajhorvath20 @.> Sent: Saturday, June 5, 2021 7:40:29 PM To: WDCommunity/wdpksrc @.> Cc: Subscribed @.***> Subject: [WDCommunity/wdpksrc] seccomp: config provided but seccomp not supported (#96)

Hi, I have this version running on My Cloud EX2 Ultra

root@Pandora-Box ~ # docker version Client: Docker Engine - Community Version: 19.03.8 API version: 1.40 Go version: go1.12.17 Git commit: Built: Thu Mar 12 10:31:28 2020 OS/Arch: linux/arm Experimental: false

And thats the output I am getting

root@Pandora-Box ~ # docker run -d -p 9000:9000 --name=portainer --restart=always -v /var/run/docker.sock:/var/run/docker.sock -v /shares/Docker/portainer:/data portainer/portainer-ce 766967c69216cf917ef04e2d73266c9f224c079410ffbb988a18ea778aed0126 docker: Error response from daemon: OCI runtime create failed: container_linux.go:349: starting container process caused "seccomp: config provided but seccomp not supported": unknown. ERRO[0009] error waiting for container: context canceled

root@Pandora-Box ~ # docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES root@Pandora-Box ~ # docker ps -a CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 766967c69216 portainer/portainer-ce "/portainer" 8 minutes ago Created 8000/tcp, 0.0.0.0:9000->9000/tcp portainer

Need little help to fix the issue.

Thanks

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHubhttps://github.com/WDCommunity/wdpksrc/issues/96, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ADMYAD2JJDKWYV3LJ3UQ57TTRHWI3ANCNFSM46EKRZJQ.

[JediNite]

@ajhorvath20,

How did you go with upgrading docker to a newer release ?

JediNite

[Vasco-90]

Download this binaries: https://github.com/JediNite/docker-ce-WDEX4100-binaries/releases/download/v20.10.7/docker-20.10.7.tgz

find the docker installation on the terminal by typing find / -name docker -type d (my dir was at /mnt/HD/HD_a2/Nas_Prog/docker/docker).

replace all files you already downloaded.

try it out by docker run hello-world.

hope this will help

[JediNite]

Download this binaries: https://github.com/JediNite/docker-ce-WDEX4100-binaries/releases/download/v20.10.7/docker-20.10.7.tgz

Hi all,

Latest (and potentially last build available) is https://github.com/JediNite/docker-ce-WDEX4100-binaries/releases/download/v20.10.17/docker-20.10.17.tgz. There are issues with compiling new builds due to Debian compatibility issues.

Cheers,

JediNite