[GH-ISSUE #1478] Netbird Signal Container does not run on AWS ECS due to missing binaries. #2530

Open
opened 2026-08-05 00:47:38 -04:00 by saavagebueno · 0 comments
Owner

Originally created by @joshuahigginson1 on GitHub (Jan 17, 2024).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/1478

Describe the problem
When trying to run the dockerhub container on Amazon ECS, the distroless container backing netbird signal does not launch. It errors with an unidentifiable error message (This is a separate AWS issue.)

The container runs absolutely fine after re-building the image with the following Dockerfile:

# Use AWS Bottlerocket as the base image.
FROM amazonlinux:latest

# Set the working directory
WORKDIR /app

# Copy the netbird-signal binary from the original image.
COPY --from=netbirdio/signal:0.25.4 /go/bin/netbird-signal /app/netbird-signal

# Ensure ownership of the file for the nobody user.
RUN chown nobody:nobody /app/netbird-signal && chmod +x /app/netbird-signal

# Set the entry point and default command.
ENTRYPOINT [ "/app/netbird-signal", "run" ]
CMD ["--log-file", "console"]

# Specify a non-root user
USER nobody

Perhaps it would be worth updating the base image to support AWS fargate functionality off the bat.
To Reproduce
Steps to reproduce the behavior:

  1. Deploy on AWS ECS using the current container held inside of dockerhub - netbirdio/netbird:0.25.4

Expected behavior
A clear and concise description of what you expected to happen.

  1. Error logs should stream like so:
    image

NetBird status -d output:
If applicable, add the output of the netbird status -d command

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

Originally created by @joshuahigginson1 on GitHub (Jan 17, 2024). Original GitHub issue: https://github.com/netbirdio/netbird/issues/1478 **Describe the problem** When trying to run the dockerhub container on Amazon ECS, the distroless container backing netbird signal does not launch. It errors with an unidentifiable error message (This is a separate AWS issue.) The container runs absolutely fine after re-building the image with the following Dockerfile: ``` # Use AWS Bottlerocket as the base image. FROM amazonlinux:latest # Set the working directory WORKDIR /app # Copy the netbird-signal binary from the original image. COPY --from=netbirdio/signal:0.25.4 /go/bin/netbird-signal /app/netbird-signal # Ensure ownership of the file for the nobody user. RUN chown nobody:nobody /app/netbird-signal && chmod +x /app/netbird-signal # Set the entry point and default command. ENTRYPOINT [ "/app/netbird-signal", "run" ] CMD ["--log-file", "console"] # Specify a non-root user USER nobody ``` Perhaps it would be worth updating the base image to support AWS fargate functionality off the bat. **To Reproduce** Steps to reproduce the behavior: 1. Deploy on AWS ECS using the current container held inside of dockerhub - netbirdio/netbird:0.25.4 **Expected behavior** A clear and concise description of what you expected to happen. 1. Error logs should stream like so: <img width="810" alt="image" src="https://github.com/netbirdio/netbird/assets/65719561/15cc702b-6fb8-416b-9200-cfb4b784f2b7"> **NetBird status -d output:** If applicable, add the output of the `netbird status -d` command **Screenshots** If applicable, add screenshots to help explain your problem. **Additional context** Add any other context about the problem here.
saavagebueno added the bugthird-party-integration labels 2026-08-05 00:47:38 -04:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#2530