Envoy 1.30.0 docker image is not working. It is crashing while creating container

[Gaurav0411GitHub]

podman pull envoyproxy/envoy:v1.30.0 Resolved "envoyproxy/envoy" as an alias (/var/cache/containers/short-name-aliases.conf) Trying to pull docker.io/envoyproxy/envoy:v1.30.0... Getting image source signatures Copying blob cc936e1c1c7b done Copying blob 5806e3fdc9eb done Copying blob 3c645031de29 done Copying blob 37a32799fc5d done Copying blob ffba67fdca1b done Copying blob 7ab97aeb917d done Copying blob 4f4fb700ef54 skipped: already exists Copying blob 5c691589cd4a done Copying blob eb66efa4427b done Copying config d2b56370bb done Writing manifest to image destination Storing signatures d2b56370bbf9e281f01d8e4c14d20408fc97fda48af94bfb1e12592bdb615b23

podman run -d -it --name envoycontainer -d envoyproxy/envoy

Container is created but it is giving some error.

2024-04-19T12:50:49.822803981+05:30 [2024-04-19 07:20:49.822][1][info][main] [source/server/server.cc:861] runtime: {} 2024-04-19T12:50:49.823196739+05:30 [2024-04-19 07:20:49.823][1][info][admin] [source/server/admin/admin.cc:66] admin address: 0.0.0.0:9901 2024-04-19T12:50:49.823379600+05:30 [2024-04-19 07:20:49.823][1][info][config] [source/server/configuration_impl.cc:168] loading tracing configuration 2024-04-19T12:50:49.823389154+05:30 [2024-04-19 07:20:49.823][1][info][config] [source/server/configuration_impl.cc:124] loading 0 static secret(s) 2024-04-19T12:50:49.823389154+05:30 [2024-04-19 07:20:49.823][1][info][config] [source/server/configuration_impl.cc:130] loading 1 cluster(s) 2024-04-19T12:50:49.823568166+05:30 [2024-04-19 07:20:49.823][1][critical][assert] [source/common/common/posix/thread_impl.cc:147] assert failure: false. Details: Unable to create a thread with return code: 1 2024-04-19T12:50:49.823591269+05:30 [2024-04-19 07:20:49.823][1][critical][backtrace] [./source/server/backtrace.h:127] Caught Aborted, suspect faulting address 0x6500000001 2024-04-19T12:50:49.823591269+05:30 [2024-04-19 07:20:49.823][1][critical][backtrace] [./source/server/backtrace.h:111] Backtrace (use tools/stack_decode.py to get line numbers): 2024-04-19T12:50:49.823600739+05:30 [2024-04-19 07:20:49.823][1][critical][backtrace] [./source/server/backtrace.h:112] Envoy version: 50ea83e602d5da162df89fd5798301e22f5540cf/1.30.0/Clean/RELEASE/BoringSSL 2024-04-19T12:50:49.823600739+05:30 [2024-04-19 07:20:49.823][1][critical][backtrace] [./source/server/backtrace.h:114] Address mapping: 56016f266000-560171c0d000 /usr/local/bin/envoy 2024-04-19T12:50:49.823919649+05:30 [2024-04-19 07:20:49.823][1][critical][backtrace] [./source/server/backtrace.h:121] #0: [0x7f35a3592520] 2024-04-19T12:50:49.823942791+05:30 [2024-04-19 07:20:49.823][1][critical][backtrace] [./source/server/backtrace.h:127] Caught Segmentation fault, suspect faulting address 0x0 2024-04-19T12:50:49.823942791+05:30 [2024-04-19 07:20:49.823][1][critical][backtrace] [./source/server/backtrace.h:111] Backtrace (use tools/stack_decode.py to get line numbers): 2024-04-19T12:50:49.823951770+05:30 [2024-04-19 07:20:49.823][1][critical][backtrace] [./source/server/backtrace.h:112] Envoy version: 50ea83e602d5da162df89fd5798301e22f5540cf/1.30.0/Clean/RELEASE/BoringSSL 2024-04-19T12:50:49.823951770+05:30 [2024-04-19 07:20:49.823][1][critical][backtrace] [./source/server/backtrace.h:114] Address mapping: 56016f266000-560171c0d000 /usr/local/bin/envoy 2024-04-19T12:50:49.824102663+05:30 [2024-04-19 07:20:49.824][1][critical][backtrace] [./source/server/backtrace.h:121] #0: [0x7f35a3592520] 2024-04-19T12:50:49.824102663+05:30 Our FatalActions triggered a fatal signal. 2024-04-19T12:51:12.799680283+05:30 E0419 07:21:12.799596787 1 thd.cc:157] pthread_create failed: Operation not permitted 2024-04-19T12:51:12.799680283+05:30 E0419 07:21:12.799664198 1 thd.cc:157] pthread_create failed: Operation not permitted 2024-04-19T12:51:12.799755625+05:30 E0419 07:21:12.799701077 1 thd.cc:157] pthread_create failed: Operation not permitted 2024-04-19T12:51:12.801151218+05:30 [2024-04-19 07:21:12.801][1][info][main] [source/server/server.cc:428] initializing epoch 0 (base id=0, hot restart version=11.104) 2024-04-19T12:51:12.801151218+05:30 [2024-04-19 07:21:12.801][1][info][main] [source/server/server.cc:430] statically linked extensions:

[adisuissa]

@phlax Not sure how this could happen, but want to rule out anything that could've gone bad on the publishing side.

I think the error is:

[source/common/common/posix/thread_impl.cc:147] assert failure: false. Details: Unable to create a thread with return code: 1

@Gaurav0411GitHub could it be related to the config you are using? If you use a vanilla config will it still crash?

[phlax]

i tested earlier ...

$ docker run --rm envoyproxy/envoy:v1.30.0

starts the server as expected

[Gaurav0411GitHub]

I have not provided any config. I have just run the below command //For pulling the image from docker hub podman pull envoyproxy/envoy:v1.30.0 //For runing the container from image podman run -d -it --name envoycontainer -d envoyproxy/envoy

I want to create container using the envoy 1.30.0 image. so that I can compile the envoy code and can take the envoy executable out of it. I am not able to do as container is giving such errors

[phlax]

fwiw this also wfm locally

$ podman run --rm docker.io/envoyproxy/envoy:v1.30.0

[adisuissa]

Looking at https://github.com/envoyproxy/envoy/blob/34bd1df90994d6d4d25ac6ff3d3209c5660fe48d/source/common/common/posix/thread_impl.cc#L154 I think you are getting an EPERM error. Not sure how it is configured, but seems there's an issue where the process running in the container doesn't have permissions to create threads.

[Gaurav0411GitHub]

But Container should not have this kind of problem, Which permission should I give it to run?

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions.

[github-actions[bot]]

This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as "help wanted" or "no stalebot". Thank you for your contributions.