dockerfile | some personally made dockerfile

I'm trying to docerize my NodeJS API together with a MySQL image. Before the initial run, I want to run Sequelize migrations and seeds to have the tables up and ready to be served.

Here's my docker-compose.yaml:

I have a dockerfile that works by itself, with

docker build -t image_apache .
docker run -tid -p 5000:80 --name=container_apache image_apache

This works, and I can connect to its webserver with 127.0.0.1:5000

But when I try to create a docker-compose.yml file to build and run the image with docker-compose, it doesn't appear to expose the port at all.

Here is the docker-compose.yaml

There is a Java 11 (SpringBoot 2.5.1) application with simple workflow:

1. Upload archives (as multipart files with size 50-100 Mb each)
2. Unpack them in memory
3. Send each unpacked file as a message to a queue via JMS

When I run the app locally java -jar app.jar its memory usage (in VisualVM) looks like a saw: high peaks (~ 400 Mb) over a stable baseline (~ 100 Mb).

When I run the same app in a Docker container memory consumption grows up to 700 Mb and higher until an OutOfMemoryError. It appears that GC does not work at all. Even when memory options are present (java -Xms400m -Xmx400m -jar app.jar) the container seems to completely ignore them still consuming much more memory.

So the behavior in the container and in OS are dramatically different. I tried this Docker image in DockerDesktop Windows 10 and in OpenShift 4.6 and got two similar pictures for the memory usage.

Dockerfile

I'm trying to follow instructions on this guide but under docker.

I set up a folder with:

I have a docker-compose.yml similar to:

I encountered a permission error while trying to build a docker container in a React app.
I tried to make use of the community answers, but didn't help.
Following related discussion I tried:

• I get the current user: id -un
• tried this: sudo chown -R myUser:myUser /usr/local/lib/node_modules
• this also threw the same error: sudo chown -R ownerName: /usr/local/lib/node_modules
• same with this: sudo chown -R $USER /usr/local/lib/node_modules
• adding a user didn't help: sudo chown -R $USER /app/node_modules
• tried to give permission installing this: sudo npm install -g --unsafe-perm=true --allow-root
• another try was to remove node_modules and install specifying sudo: sudo npm install

Adding this to docker-compose file, didn't help either:

I can't compile DPDK inside a docker container, running under WSL2 as VM (and windows 10 as the host machine).

Background

Trying to compile DPDK locally inside a wsl-container some DPDK lib that used to be built on remote native linux machines.

The Dockerfile running the compilation had installed kernel headers, GNU toolchain and other various dependencies. The distribution is CentOS7.

The containers are managed by Docker Desktop

Versions are useless information here.

The Problem

Similar problems across DPDK versions. In DPDK 20.11, using the meason build-system, the file kernel/linux/meason.build:

../kernel/linux/meson.build:23:1: ERROR: Problem encountered: Cannot compile kernel modules as requested - are kernel headers installed?

If I compile different DPDK versions of DPDK or building using other build-systems (makefiles), I am getting variants of the same error.

Before I run eb create command, how can I tell Elastic Beanstalk to use a DIFFERENT docker-compose file?

For example, my project directory:

I have a simple echo.sh file with this: echo "hello" (with or without #!/bin/bash it gives the same error)

this command immediately returns even though there is a echo.sh in this place in the container: