HTTP service running inside a container gives connection timeout error

[TharmiganK]

Description

$Subject

This is happening for the new HTTP patch version: 2.15.5 which only has the netty vulnerability fix.

Steps to Reproduce

Run the following service inside a docker container:

import ballerina/http;

final http:Client postmanClient = check new ("https://postman-echo.com");

service / on new http:Listener(9090) {
    resource function get greeting(string? name) returns string|error {
        if name is () {
            return error("name should not be empty!");
        }
        return postmanClient->/post.post(string `Hello, ${name}`);
    }
}

Error:

time=2025-02-13T14:46:46.931Z level=ERROR module=ballerina/http message="unhandled error returned from the service" error={"causes":[{"message":"Connection timeout: postman-echo.com/100.24.216.48:443","detail":{},"stackTrace":[]}],"message":"Something wrong with the connection","detail":{},"stackTrace":[]} path="/greeting?name=Tharmi" method="GET"

Version

Ballerina SwanLake Update 10

Environment Details (with versions)

No response

[TharmiganK]

The cause of the failure:

java.lang.UnsatisfiedLinkError: failed to load the required native library
java.lang.IllegalArgumentException: Failed to load any of the given libraries: [netty_tcnative_linux_x86_64, netty_tcnative_linux_x86_64_fedora, netty_tcnative_x86_64, netty_tcnative]

Failed to load the required native libraries at runtime in the docker environment. It seems like some other native library may be missing in the docker environment. Downgrading the netty-tcnative version to 2.0.66-Final seems to be working. Until the root cause is found, downgrading only the netty-tcnative version might be a resolution. (Changes between 2.0.66 and 2.0.67)

[TharmiganK]

Changing the base image to eclipse-temurin:17-jdk using the Cloud.toml worked. So, it seems like some native library linked in the latest tcnative version is missing in the base image we are using in our c2c.

[container.image]
base="eclipse-temurin:17-jdk"

[TharmiganK]

This may be related to this issue: #2803. May be the missing glibc in the default base image, might be the problem.

@anuruddhal What should be the resolution for issues like this:

• Option 1: Change to a compatible base image, if you encounter such issue. We should have proper documentation for this
• Option 2: By default, use a glibc compatible base image in c2c