-
Notifications
You must be signed in to change notification settings - Fork 5.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wordpress-nginx image using apache #76514
Labels
solved
tech-issues
The user has a technical issue about an application
triage
Triage is needed
wordpress-nginx
Comments
bashbang
added
the
tech-issues
The user has a technical issue about an application
label
Jan 23, 2025
I'm not able to reproduce the issue using the latest $ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
c4542e800c46 bitnami/wordpress-nginx:6 "/opt/bitnami/script…" 8 seconds ago Up 8 seconds 0.0.0.0:80->8080/tcp, 0.0.0.0:443->8443/tcp projects-wordpress-1
feff01c7a94e bitnami/mariadb:latest "/opt/bitnami/script…" 8 seconds ago Up 8 seconds 3306/tcp projects-mariadb-1
$ docker top c4542e800c46
UID PID PPID C STIME TTY TIME CMD
1001 1806 1756 0 11:48 ? 00:00:00 /bin/bash /opt/bitnami/scripts/nginx-php-fpm/run.sh
1001 2308 1806 0 11:49 ? 00:00:00 php-fpm: master process (/opt/bitnami/php/etc/php-fpm.conf)
1001 2310 1806 0 11:49 ? 00:00:00 nginx: master process /opt/bitnami/nginx/sbin/nginx -c /opt/bitnami/nginx/conf/nginx.conf -g daemon off;
1001 2313 2310 0 11:49 ? 00:00:00 nginx: worker process
1001 2314 2310 0 11:49 ? 00:00:00 nginx: worker process
1001 2315 2310 0 11:49 ? 00:00:00 nginx: worker process
1001 2316 2310 0 11:49 ? 00:00:00 nginx: worker process
1001 2317 2310 0 11:49 ? 00:00:00 nginx: worker process
1001 2318 2310 0 11:49 ? 00:00:00 nginx: worker process
1001 2319 2310 0 11:49 ? 00:00:00 nginx: worker process
1001 2320 2310 0 11:49 ? 00:00:00 nginx: worker process
1001 2321 2310 0 11:49 ? 00:00:00 nginx: worker process
1001 2322 2310 0 11:49 ? 00:00:00 nginx: worker process Could you please ensure you're not using the regular |
I installed a fresh docker file and fresh build/install. I must have had my docker wires crossed. You are correct. wordpress-nginx:6.7.1 is running nginx as expected. Sorry for sharing my confusion. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
solved
tech-issues
The user has a technical issue about an application
triage
Triage is needed
wordpress-nginx
Name and Version
bitnami/wordpress-nginx:6.7.1
What architecture are you using?
amd64
What steps will reproduce the bug?
With an update to my existing FROM bitnami/wordpress-nginx:6.6.1 to FROM bitnami/wordpress-nginx:6.7.1 I'm no longer running nginx server on the container, it's now running apache:
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND root 1 0.3 0.2 262680 41936 ? Ss 23:07 0:00 apache2 -DFOREGROUND www-data 58 0.0 0.0 262720 12640 ? S 23:07 0:00 apache2 -DFOREGROUND
What is the expected behavior?
The Nginx is the webserver running the wordpress service.
root 1 0.0 0.0 4860 3940 ? Ss 23:27 0:00 /bin/bash /opt/bitnami/scripts/nginx-php-fpm/run.sh root 386 0.1 0.2 306040 41180 ? Ss 23:27 0:00 php-fpm: master process (/opt/bitnami/php/etc/php-fpm.conf) root 388 0.0 0.0 11724 9076 ? S 23:27 0:00 nginx: master process /opt/bitnami/nginx/sbin/nginx -c /opt/bitnami/nginx/conf/nginx.conf -g daemon off; daemon 391 0.0 0.0 12236 5228 ? S 23:27 0:00 nginx: worker process
What do you see instead?
I see Apache server running
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND root 1 0.3 0.2 262680 41936 ? Ss 23:07 0:00 apache2 -DFOREGROUND www-data 58 0.0 0.0 262720 12640 ? S 23:07 0:00 apache2 -DFOREGROUND
Additional information
bitnami/wordpress-nginx:6.6.1 works as expected.
The text was updated successfully, but these errors were encountered: