Why am I receiving a "user does not exist" error when building my Docker app on App Platform?

If your Docker App on App Platform fails to build with the following error in the deployment logs, then the USER instruction may be in the wrong place in your Dockerfile:

error building image: error building stage: failed to execute command: identifying uid and gid for user app: user app is not a uid and does not exist on the system

In a Dockerfile, each instruction builds on the state created by the previous instructions. If the USER instruction is before a FROM or WORKDIR instruction, the FROM and WORKDIR instruction fail to execute because the user ID doesn’t exist in the base image or work directory yet.

To fix this, make sure the line with the USER instruction is after the lines with the FROM and WORKDIR instructions in your Dockerfile:

FROM example-image:latest AS base
WORKDIR /example/dir
USER example-user
EXPOSE 80
 

After you update the Dockerfile in your repository, your Docker app automatically redeploys on App Platform.

Related Topics

Why am I receiving an "invalid dockerfile_path" error when building my Docker app on App Platform?

Ensure your Dockerfile’s path is correctly defined using the dockerfile_path parameter in your app spec file.

Why does my app not restart when it fails a health check?

If an app’s health check fails, the app currently does not restart. This is because App Platform does not currently support liveness probes. An app only automatically restarts if the app crashes or if its disk or RAM usage exceeds the its limits.

Where can I find the client IP address of a request connecting to my app?

You can find the client IP address of a request connecting to your app in the do-connecting-ip HTTP header.