Redhat UBI镜像中Nginx无法在81端口启动的问题求助

Let’s walk through fixing your issue step by step—here’s what’s probably going wrong and how to resolve it:

1. You’re not actually using your custom nginx.conf #

Looking at your Dockerfile, the line that copies your modified config into the container is commented out (#COPY nginx.conf /etc/nginx/nginx.conf). That means Nginx is still using the default configuration (which listens on port 80) instead of your port-81 setup. Fix this by uncommenting that line:

FROM registry.access.redhat.com/ubi8/ubi8-minimal
RUN microdnf --setopt=tsflags=nodocs install -y nginx procps net-tools ca-certificates dirmngr gnupg wget vim\
    && microdnf clean all \
    && rpm -q procps-ng
COPY nginx.conf /etc/nginx/nginx.conf  # Uncomment this line to use your custom config!
EXPOSE 81
CMD ["nginx", "-g", "daemon off;"]

2. Validate your nginx.conf syntax #

Even if you copy the file, a syntax error will crash Nginx on startup. Test the config’s validity (either locally or inside a running container shell) with:

nginx -t

If you get an error like nginx: [emerg] invalid..., fix the problematic line in your config—common issues include typos in proxy_pass URLs or unclosed brackets.

3. Check for port conflicts inside the container #

Another process might be hogging port 81. To debug this, start your container with a shell instead of Nginx first:

docker run -it --rm your-image-tag bash

Inside the container, run these commands to check for processes listening on 81:

# Using netstat
netstat -tulpn | grep 81
# Or ss (more modern alternative)
ss -tulpn | grep 81

If you see a process listed, stop it or switch to a different unused port.

4. Inspect Nginx startup logs for specific errors #

When you start the container, check the logs to see exactly why Nginx is failing—this is the fastest way to pinpoint issues:

# If starting a new container
docker run your-image-tag
# If the container was already created (replace <container-id> with your container's ID)
docker logs <container-id>

Common errors here include "address already in use", "invalid configuration directive", or (rarely for port 81) permission denied (since ports above 1024 don’t require root privileges).

5. Rule out SELinux blocking the port #

Red Hat UBI has SELinux enabled by default, which might restrict Nginx to only listen on standard HTTP ports (like 80). To test if this is the issue, temporarily set SELinux to permissive mode inside the container:

setenforce 0

If Nginx starts successfully after this, you’ll need to add a custom SELinux policy to allow Nginx to use port 81. First install the required tools:

microdnf install policycoreutils-python-utils

Then add the port to the allowed list:

semanage port -a -t http_port_t -p tcp 81

Final Test #

After making these fixes, rebuild your image and run it:

docker build -t nginx-ubi8-custom .
docker run -p 81:81 nginx-ubi8-custom

You should now be able to access Nginx on http://localhost:81.

内容的提问来源于stack exchange，提问作者M B