Can't run greengrass v1.7 in a docker container on CentOS

dzimine commented 5 years ago

Tried docker on CentOS. After installing and downgrading it per this bug, still no luck: the greengrass daemon doesn't start:

Setting up greengrass daemon
Validating hardlink/softlink protection
Waiting for up to 40s for Daemon to start
panic: failed to clone executable onto a write-sealed copy: create clone-to binary: memfd_create ggc_cloned:/proc/self/exe: invalid argument

goroutine 1 [running]:
amazonaws.com/iot/greengrass/system/cloneBinary.ensureSelfCloned(0xc9877b, 0x13)
    /codebuild/output/src164823672/src/GoAmzn-GreengrassDaemon/src/amazonaws.com/iot/greengrass/system/cloneBinary/cloneBinary.go:100 +0x2ae
The Greengrass daemon process with [pid = 9] died

Environment:

[vagrant@localhost ~]$ docker version
Client:
 Version:           18.09.2
 API version:       1.39
 Go version:        go1.10.6
 Git commit:        6247962
 Built:             Sun Feb 10 04:13:27 2019
 OS/Arch:           linux/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          18.09.2
  API version:      1.39 (minimum version 1.12)
  Go version:       go1.10.6
  Git commit:       6247962
  Built:            Sun Feb 10 03:47:25 2019
  OS/Arch:          linux/amd64
  Experimental:     false

Dockerfile:

FROM ubuntu:trusty

RUN adduser --system ggc_user \
    && groupadd --system ggc_group

RUN apt-get update \
    && apt-get install -y sqlite3 python2.7 binutils

ADD downloads/greengrass-linux-x86-64-1.7.1.tar.gz /

RUN apt-get install -y ca-certificates

EXPOSE 8883

COPY start.sh /

ENTRYPOINT ["/start.sh"]

rgeissen commented 4 years ago

Did you manage to come up with a solution for this? I get the same error message when I am trying to run the official aws greengrass docker image on my synology nas ... any feedback would be appreciated.

00p6wise commented 3 years ago

Any solutions?

dzimine / aws-greengrass-docker

Can't run greengrass v1.7 in a docker container on CentOS #7