Dockerfile中ARG与ENV配置不生效问题求助

Hey there, let's work through why your ARG and ENV settings aren't taking effect in that WebLogic Dockerfile. I've tackled similar problems with Oracle's official WebLogic images before, so here are targeted checks and fixes to try:

Common ARG Pitfalls to Fix #

• ARG only exists during build time: If you need the value to be available when the container runs, you have to convert it to an ENV. For example:

  ARG MY_DOMAIN=base_domain
  ENV DOMAIN_NAME=$MY_DOMAIN
  

  This ensures the value sticks around for runtime processes like starting WebLogic.
• Position matters with ARG: ARGs defined before the FROM line only work within the FROM instruction itself. Any ARGs you want to use in build steps (like RUN, COPY) need to be declared after FROM:

  # This ARG only affects the FROM line
  ARG WL_VERSION=12.2.1.4
  FROM oracle/weblogic:$WL_VERSION
  # This ARG works for all subsequent build steps
  ARG ADMIN_PASSWORD=Welcome1
  

• Don't forget to pass ARGs at build time: If you defined an ARG without a default value, or want to override the default, you need to pass it with --build-arg when building:

  docker build --build-arg ADMIN_PASSWORD=MySecurePass123 --no-cache .
  

  The --no-cache flag is critical here to avoid using outdated cached build steps.

ENV Issues to Diagnose #

• Check the order of your instructions: If you set an ENV after the step that needs it (like a RUN command that creates the WebLogic domain), the value won't be available. Always define ENVs before the steps that rely on them.
• Make sure you aren't overwriting ENVs: Double-check your Dockerfile for later ENV commands that might overwrite the values you set earlier. For example, if you set ENV ADMIN_PORT=7001 then later have ENV ADMIN_PORT=8080, the first value gets lost.
• Verify runtime overrides: If you're starting the container with docker run -e ADMIN_PORT=9000 ... or using a docker-compose environment block, those values will override the ENV settings baked into the image. Run docker run --rm your-image-name env to see what ENVs are actually present at runtime.

WebLogic-Specific Checks #

Oracle's WebLogic images have some unique behaviors to keep in mind:

• Use recognized environment variables: The official WebLogic images are built to respond to specific pre-defined ENVs (like ADMIN_PASSWORD, DOMAIN_NAME, NM_PORT). If you're using custom ENVs, make sure your domain creation scripts explicitly reference them (e.g., using $DOMAIN_NAME instead of hardcoding a domain name).
• Check startup scripts: The default startWebLogic.sh or startNodeManager.sh scripts might not pick up arbitrary ENVs unless you modify them or pass the values explicitly when starting the services. For example, you might need to update your domain's setDomainEnv.sh to include your custom ENVs.

Quick Debugging Steps #

1. Run docker history your-image-name to review the build steps and confirm ARGs were applied correctly.
2. Use docker run --rm your-image-name printenv to list all runtime environment variables and verify your ENVs are present.
3. Rebuild with --no-cache to rule out cached build steps causing old values to persist.

Here's a quick example of a corrected Dockerfile snippet that properly uses ARG and ENV for WebLogic:

FROM oracle/weblogic:12.2.1.4

# Build-time args with defaults
ARG DOMAIN_NAME=my_custom_domain
ARG ADMIN_PORT=7001

# Convert to runtime ENVs
ENV DOMAIN_NAME=$DOMAIN_NAME
ENV ADMIN_PORT=$ADMIN_PORT

# Copy and run domain creation script that uses the ENVs
COPY create_custom_domain.sh /u01/oracle/
RUN chmod +x /u01/oracle/create_custom_domain.sh && /u01/oracle/create_custom_domain.sh

EXPOSE $ADMIN_PORT

内容的提问来源于stack exchange，提问作者Tuomas Toivonen