MemLock | MemLock : Memory Usage | Speech library

As per the discussion in the comments, the map is not created because it is not actually used in your eBPF code (not provided in the question).

As you realised yourself, the branch in your code that was calling the map was in fact unreachable. Based on that, it's likely that clang compiled out this portion of code, and that the map is not used in the resulting eBPF bytecode. When preparing to load your program, bpftool (libbpf) looks at what maps are necessary, and only creates the ones that are needed for your program. It may skip maps that are defined in the ELF file if no program uses them.

One hint here is that, if the program was effectively using the map, it couldn't load successfully if the map was missing: given that your program loads, the map would necessarily be present if it was needed. Note that bpftool prog show will show you the ids of the maps used by a program.

I have solved this problem.

I had to make the following changes to the following files:

sudo nano /etc/systemd/user.conf add DefaultLimitSTACK=134217728

sudo nano /etc/systemd/system.conf add DefaultLimitSTACK=134217728

Make sure the number you define is a power of 2, else Ubuntu fails to login for some reason.

I have 128GB of RAM. So I have set my limit to 2^27.

Hope this helps someone with the same problem.

Try this :

If you want to connect elasticsearch with docker, change your host to container name.

I had the same issue on the mac. But it gets resolved when I increase the memory size in docker-desktop

I entered the container from the runner machine while the ci was running and I noticed that the repository was cloned as root but the build directories were created under a user. The cofigure_file command is trying to modify a file from the repository, so it's like user is trying to modify a file created as root (when cloned). I didn't manage to make the gitlab-runner software clone the repository as user. Instead, my workaround was to change the permissions of the folder before building. My .gitlab-ci.yml looks like this now

Based on the documentation, Docker Swarm automatically creates the overlay network for you. So I think you don't need to create an external network by default, unless you have specific needs:

When you initialize a swarm or join a Docker host to an existing swarm, two new networks are created on that Docker host:

• an overlay network called ingress, which handles the control and data traffic related to swarm services. When you create a swarm service and do not connect it to a user-defined overlay network, it connects to the ingress network by default.
• a bridge network called docker_gwbridge, which connects the individual Docker daemon to the other daemons participating in the swarm.

As Chris also mentioned in the comments, the DB credentials also don't match.

OPTIONAL: MYSQL_ROOT_HOST is only necessary if you want to connect as root user which is not recommended in production environments. There's also no need to expose the port to the host machine since the database service will only be used from inside the cluster. So if you still want to use root user, you can set the variable to allow connections only from inside the cluster, like MYSQL_ROOT_HOST=10.*.*.*.

try using rsync utility it's well suited with large files

distribute cluster instances to different hosts(with different IP addresses) and also enable communications between these es instances?

This is exactly the use case for Kubernetes or Docker Swarm (if you must have containers).

https://www.elastic.co/blog/introducing-elastic-cloud-on-kubernetes-the-elasticsearch-operator-and-beyond