UNCLASSIFIED - NO CUI

Skip to content

nginx 1.26.0 does not startup

Summary

The latest version of this image (1.26.0) no longer starts up.

Steps to reproduce

Attempt to run the container:

For example, you could run the below to test it locally in Docker.

docker run -it registry1.dso.mil/ironbank/opensource/nginx/nginx-alpine:1.26.0

What is the current bug behavior?

the docker entry point script runs, but nginx itself just slightly exits:

What is the expected correct behavior?

nginx should start up and stay running until the container is closed (ie. ctl+c)

Relevant logs and/or screenshots

docker run -it registry1.dso.mil/ironbank/opensource/nginx/nginx-alpine:1.26.0
/docker-entrypoint.sh: /docker-entrypoint.d/ is not empty, will attempt to perform configuration
/docker-entrypoint.sh: Looking for shell scripts in /docker-entrypoint.d/
/docker-entrypoint.sh: Launching /docker-entrypoint.d/10-listen-on-ipv6-by-default.sh
10-listen-on-ipv6-by-default.sh: info: /etc/nginx/conf.d/default.conf is not a file or does not exist
/docker-entrypoint.sh: Launching /docker-entrypoint.d/20-envsubst-on-templates.sh
/docker-entrypoint.sh: Launching /docker-entrypoint.d/30-tune-worker-processes.sh
/docker-entrypoint.sh: Configuration complete; ready for start up

Possible fixes

I'm also experiencing the same issue on my container that uses the 1.25.3 tag. See dsop/keysight/eggplant/dai-ai-ui#13 (closed)

The issue seems to be the version of libcrypto3. (the odity on my container is that it seems to have the alpine 3.20 version of libcrypto3 installed in a 3.19.1).

Tasks

  • Bug has been identified and corrected within the container

Please read the Iron Bank Documentation for more info

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information