su-exec | switch user and group id and exec | Automation library

You are installing some statically compiled dependencies in your Docker environment, like libc-dev, geos-dev, and geos. You have to also include those static dependencies in the Lambda deployment zip file. Also, to include statically compiled dependencies for use in AWS Lambda you have to use the same operating system Lambda uses, which is Amazon Linux, not Alpine Linux.

Luckily there are two alternatives now that make this much easier:

Lambda Layers

Lambda Layers are Lambda dependencies that can be packaged up in a reusable method, that can also be shared with other developers. In this case someone has already created a shapely Lambda Layer (and someone else here) that you can simply include in your Lambda function instead of trying to package it yourself.

If you still want to build it yourself you could look at that project's source code to see how they are building the layer.

Lambda Containers

Instead of creating a zip deployment, you could create a Docker image and deploy it to Lambda. You do have to implement a specific interface inside your Lambda container if you go this route, and it is easiest to do this by starting with one of the official AWS Lambda base images.

Try to use set -- su -c elasticsearch tini -- "$@"

Also you do not need to define CMD ["elasticsearch"] inside Dockerfile. Just put inside elastic-entrypoint.sh file.

On the Docker VM run ls /home/ and I would wager the directory you expect isn't there. The user referenced in your path probably doesn't exist on the VM, only on your host machine.

The relative path works because it's relative to the root directory provided.

The OCI message is just part of how Alpine reports an error. But your actual error is in the CMD line.

Your syntax is not correct. Either you remove the [] or add as comma a @jakub pointed out.

https://docs.docker.com/engine/reference/builder/#cmd

That is the way Docker works - it keeps a container up only while the process started by initial arguments is running. new-initfile.sh completes all the lines and exits normally and so does the container.

In general you need an endless task at the end of your entrypoint script so that it never exits unless an error or a stop signal happens. In your case, I would have delegated migrations to the application rather that the database. It is common to run migrations before starting an application and it's more convenient when you add new migrations (you don't have to mess with two images).

If you still wish the database to do migrations, here are two options:

1. Postgres Docker image supports extension scripts but they only run at the first launch. That is when Postgres creates a database. It will not run extension scripts on consecutive launches. This is the best way to load a dump or something like that. To utilise the feature place the script in /docker-entrypoint-initdb.d/ inside the container. The script must have *.sql, *.sql.gz, or *.sh extension. Read more about initialization scripts here.

2. Run the following command and examine the output: docker run --rm postgres:alpine cat /usr/local/bin/docker-entrypoint.sh. This is the default entrypoint script in this image. There are a lot of code in it but look at this first:

Changes to the contents of the stubs directory are not real-time refreshed in the WireMock application. It is possible to use the Swagger UI: http://localhost:8080/__admin/swagger-ui to reset it manually or the corresponding API call to automate it.

Don't know what you are trying to achive but I would do it on OS-level.

You can create a cronjob to execute something in your container is this would help. Try to use something like this:

That su-exec error sounds like n8n requires root/elevated privileges, which you do not get on Heroku. If you have to configure it in some way to run strictly “unprivileged”, do that.

The dockerfile you're using seems to be building an image from a basic license Kibana download (which includes X-Pack) and then manually removing the x-pack directory. When plugins, such as the ones located in the x-pack directory, are disabled, Kibana needs to rebuild all javascript bundles. This process, known as the optimizer is very memory intensive and depends on the size of the code base, so the amount of memory required can change between releases.

There's a few options:

1. You could try to build your file from a OSS Kibana release, this doesn't include the x-pack plugins and shouldn't require a rebuild of javascript bundles https://www.elastic.co/downloads/past-releases/kibana-oss-7-5-2
2. Allocate more memory, 4GB should be enough.
3. Build an intermediate image with at least 4GB memory. After having been built, running the image shouldn't require such high memory usage anymore.