docker-compose-wait VS wordpress

FROM wordpress:cli # Install make tool USER root RUN apk add --no-cache make # Make docker-compose wait for container dependencies be ready # Add the wait script to the image ENV WAIT_VERSION 2.7.2 ADD https://github.com/ufoscout/docker-compose-wait/releases/download/$WAIT_VERSION/wait /wait RUN chmod +x /wait # Add Makefile to scripts dir ADD Makefile entrypoint.sh /scripts/ RUN chmod +x /scripts/entrypoint.sh ENTRYPOINT [ "/scripts/entrypoint.sh" ] USER 33:33 CMD ["wp", "shell"]

FROM mcr.microsoft.com/dotnet/sdk:5.0-alpine AS build WORKDIR /src # Get connection string argument from docker compose and set it as an environment variable ARG connection_string ENV ConnectionStrings__Database=${connection_string} # Standard docker build COPY ["tests/Integration.Tests/Integration.Tests.csproj", "Integration.Tests/"] RUN dotnet restore "Integration.Tests/Integration.Tests.csproj" COPY . . WORKDIR "Integration.Tests" # Restore the dotnet-ef command RUN dotnet tool restore RUN dotnet build "Integration.Tests.csproj" -c Release -o /app/build # Install docker-compose-wait to make sure the db server is up & running before moving on ADD https://github.com/ufoscout/docker-compose-wait/releases/download/2.5.0/wait /wait RUN chmod +x /wait # Wait for sql server and then migrate the db and run tests CMD /wait && dotnet ef database update --context MyDbContext && dotnet test --no-build

If youre using docker-compose, I can recommend https://github.com/ufoscout/docker-compose-wait

#!/bin/sh set -euo pipefail # Based on wordpress:cli entrypoint # https://github.com/docker-library/wordpress/blob/master/php7.2/cli/docker-entrypoint.sh # If the first arg is `--some-option` then execute wp-cli if [ "${1#-}" != "$1" ]; then set -- wp "$@" fi # if our command is a valid wp-cli subcommand (say plugin), let's invoke it through wp-cli instead # (this allows for "docker run wordpress:cli help", etc) # documenation of the subcommand is shown if wp --path=/dev/null help "$1" > /dev/null 2>&1; then set -- wp "$@" fi # Execute aliases in the make file or directly the provided command if [ "$1" == "install" ] || [ "$1" == "configure" ]; then make -f /scripts/Makefile $1 else exec "$@" fi

You can take a look at the dockerfile here for educational purposes and you can see apache is not configured to listen on 443 at all. And if you read the "How to use this image" section on the docker hub page for wordpress you can see that they suggest you to set up TLS using a reverse proxy like nginx and there are some additional things to set up.

In the entrypoint script for Wordpress (link here), if a folder already has content, nothing new gets written in. I'm not 100% sure that this would work, but you could try:

Additional note, look an the official WordPress dockerfile. https://github.com/docker-library/wordpress/blob/97f75b51f909fbd9894d128ea6893120cfd23979/latest/php7.4/apache/Dockerfile At the bottom you are a entrypoint and a CMD. I believe it runs "$entrypoint $CMD" when started with no arguments. Your can charge these, or best to leave alone. You just need to docker run your new built container.

Which one is it here: https://github.com/docker-library/wordpress/tree/master/latest

https://github.com/docker-library/wordpress/blob/master/docker-entrypoint.sh#L71

wordpress | WARNING: environment variable "WORDPRESS_CONFIG_EXTRA" is set, but "wp-config.php" already exists wordpress | The contents of this variable will _not_ be inserted into the existing "wp-config.php" file. wordpress | (see https://github.com/docker-library/wordpress/issues/333 for more details) w ```

WordPress already provides a docker image which can be used for development, but it has a few problems that are not dealt with in the usual docker way. We never really found a configurable solution to these problems, which always meant using the docker image requiring some repeated “must know” steps for everything the containers need to be built. Or reverting to using developer machines local php/apache/mysql or another dev environment tool.