Building Docker Image For Linux/amd64 Builds But web3.swift calls don't return

[eloit]

I am building a Vapor based application, using this module. When testing locally within Xcode, everything works fine. When I build the local Docker Image [arm], and run it on my M1 Mac, it also runs fine. This is usually where I have issues, but building and running locally all is good. The issue is when I build for Linux/amd64 where I can deploy the container in the cloud, the image builds and runs fine, but first call to EthereumHttpClient(url: clientUrl) never returns.

Please help!

I am using the standard Dockerfile that Vapor creates (uncommenting the libcurl4 so it is included)

I build the platform:

docker builds build --platform linux/amd64 -t <image name> . 

The Dockerfile:

# ================================
# Build image
# ================================
FROM swift:5.8.1-jammy as build

# Install OS updates and, if needed, sqlite3
RUN export DEBIAN_FRONTEND=noninteractive DEBCONF_NONINTERACTIVE_SEEN=true \
    && apt-get -q update \
    && apt-get -q dist-upgrade -y\
    && rm -rf /var/lib/apt/lists/*

# Set up a build area
WORKDIR /build

# First just resolve dependencies.
# This creates a cached layer that can be reused
# as long as your Package.swift/Package.resolved
# files do not change.
COPY ./Package.* ./
RUN swift package resolve

# Copy entire repo into container
COPY . .

# Build everything, with optimizations
RUN swift build -c release --static-swift-stdlib

# Switch to the staging area
WORKDIR /staging

# Copy main executable to staging area
RUN cp "$(swift build --package-path /build -c release --show-bin-path)/App" ./

# Copy resources bundled by SPM to staging area
RUN find -L "$(swift build --package-path /build -c release --show-bin-path)/" -regex '.*\.resources$' -exec cp -Ra {} ./ \;

# Copy any resources from the public directory and views directory if the directories exist
# Ensure that by default, neither the directory nor any of its contents are writable.
RUN [ -d /build/Public ] && { mv /build/Public ./Public && chmod -R a-w ./Public; } || true
RUN [ -d /build/Resources ] && { mv /build/Resources ./Resources && chmod -R a-w ./Resources; } || true

# ================================
# Run image
# ================================
FROM ubuntu:jammy

# Make sure all system packages are up to date, and install only essential packages.
RUN export DEBIAN_FRONTEND=noninteractive DEBCONF_NONINTERACTIVE_SEEN=true \
    && apt-get -q update \
    && apt-get -q dist-upgrade -y \
    && apt-get -q install -y \
      ca-certificates \
      tzdata \
# If your app or its dependencies import FoundationNetworking, also install `libcurl4`.
    libcurl4 \
# If your app or its dependencies import FoundationXML, also install `libxml2`.
      # libxml2 \
    && rm -r /var/lib/apt/lists/*

# Create a vapor user and group with /app as its home directory
RUN useradd --user-group --create-home --system --skel /dev/null --home-dir /app vapor

# Switch to the new home directory
WORKDIR /app

# Copy built executable and any staged resources from builder
COPY --from=build --chown=vapor:vapor /staging /app

# Ensure all further commands run as the vapor user
USER vapor:vapor

# Let Docker bind to port 8080
EXPOSE 8080

# Start the Vapor service when the image is run, default to listening on 8080 in production environment
ENTRYPOINT ["./App"]
CMD ["serve", "--env", "production", "--hostname", "0.0.0.0", "--port", "8080"]

[dioKaratzas]

Hey @eloit , All the calls to the EthereumHttpClient never returns or a specific one?

[eloit]

It happens in the first call.   I did update to the develop branch and that has seemed to addressed it.   I see there was an additionalNetwork parameter to resolve some deadlock issue.  That seem to have worked for now.   Handy software for sure.  Got me out of a bind. Thanks. Sent from my iPhoneOn Jul 25, 2023, at 4:26 AM, Dionysis Karatzas @.***> wrote: Hey @eloit , All the calls to the EthereumHttpClient never returns or a specific one?

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

[dioKaratzas]

Glad to hear @eloit that you resolved your issue :)