Docker Image for superset_node with node:20-bullseye-slim on linux/amd64 Fails to Run on Host Machine

[adhamenaya]

I am trying to push a Docker image for superset_node to a host machine with the platform/arch set to linux/amd64.

Here's what I've done so far:

• I successfully built the Docker image using the linux/amd64 platform architecture.
• The base image I used is node:20-bullseye-slim, which by default pulls the arm64 architecture. To resolve this, I explicitly set the platform to linux/amd64 in my Dockerfile like so:

ARG BUILDPLATFORM=${BUILDPLATFORM:-linux/amd64}
FROM --platform=linux/amd64 node:20-bullseye-slim AS superset-node

• I verified that the image and its layers are now using the linux/amd64 platform by checking the tag's command:

  Before setting the platform explicitly:

  # debian.sh --arch 'arm64' out/ 'bullseye' '@1733097600'
  

  After setting the platform explicitly:

  # debian.sh --arch 'amd64' out/ 'bullseye' '@1733097600'
  

However, after pushing the image and running it on my Docker host, the container stops immediately with no logs shown, and I see this message:

No log line matching the '' filter

What I've Tried:

• I've confirmed that the platform is correctly set to linux/amd64 and that the architecture of the base image has been properly adjusted.
• I've checked the logs but found nothing that could explain the failure.

Questions:

1. Why is the container stopping immediately with no logs, even though the correct platform and architecture have been set?
2. Is there anything else I need to configure to ensure the container runs properly on linux/amd64?
3. How can I get more detailed logs or debug information to diagnose the problem?

Any help or insight would be greatly appreciated!

[dosubot[bot]]

To address the issue of the superset_node container stopping immediately with no logs, here are a few steps and considerations:

1. Check the Entry Point and Command: Ensure that the entry point or command specified in the Dockerfile is correct. For the superset_node image, the command should be ["/app/docker/docker-frontend.sh"] ^[1]. Verify that this script exists and is executable in your image.

2. Environment Variables and Configurations: Make sure all necessary environment variables and configurations are set correctly. The superset_node container requires several environment variables, such as BUILD_SUPERSET_FRONTEND_IN_DOCKER, SUPERSET_BUILD_TARGET, and others. Ensure these are correctly configured in your environment or Docker Compose setup ^[1][2].

3. Dependencies: Confirm that the required services (db and redis) are running and accessible. The superset_node container depends on these services, and if they are not available, it might cause the container to exit ^[1].

4. Logging Configuration: Since no logs are being shown, check the logging configuration. The LOG_LEVEL is set to DEBUG if DEBUG is true, otherwise INFO. Ensure that the logging level is set appropriately to capture more detailed logs ^[3].

5. Debugging: To get more detailed logs or debug information, you can:

   • Run the container with an interactive shell to manually execute the entry point script and observe any errors.
   • Add additional logging or echo statements in the docker-frontend.sh script to capture more information about what might be failing.

6. Check for Errors in the Script: If the entry point script (docker-frontend.sh) has any errors or exits prematurely, it could cause the container to stop. Review the script for any potential issues.

By following these steps, you should be able to gather more information about why the container is stopping and address any configuration or dependency issues.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other}