Hi,

I'm facing an issue with executing the prep.sh file. Get this error:
OCI runtime exec failed: exec failed: container_linux.go:380: starting container process caused: exec: "prep.sh": executable file not found in $PATH: unknown

Not sure why this is happening. The file is copied to /usr/local/bin/prep.sh and has executable rights.

Any ideas whats happening here or how I could debug this? Thank you for your time!

Kind regards,

Hi,
Thank you for setting this up.
It looks promising the only idea of importing the PROD db dump, renaming it and importing it to docker.
Unfortunately it won't import my backup.sql.gz file located into the mysqldumps folder.
This is my docker-compose.yaml content:
db:
image: mysql:5.7
volumes:
- ./database:/var/lib/mysql
- ./mysqldumps/backup.sql.gz:/docker-entrypoint-initdb.d/backup.sql.gz
- ./init/migrate.sh:/docker-entrypoint-initdb.d/migrate.sh
restart: always
ports:
- '3306:3306'
environment:
MYSQL_ROOT_PASSWORD: default
MYSQL_DATABASE: wordpress
MYSQL_USER: $db_user
MYSQL_PASSWORD: $db_password
WORDPRESS_TABLE_PREFIX: $db_table_prefix
PRODUCTION_URL: $production_url
WP_ALLOW_MULTISITE: true

Within my .env I've only updated the production_url variable, everything else is the default .env located on this repo:

(Required) The table prefix of the WordPress database used in production site

E.g wp_

db_table_prefix=wp_

(Optional) You can disable certain plugins that are not needed for development, e.g. security or SEO plugins.

Comma separated string (no spaces), leave blank if no plugins to disable.

E.g. plugin-folder-name-1,plugin-folder-name-2

wp_plugins_to_disable=

####################################################

Defaults - can be left as-is for basic usage

####################################################
db_host=db:3306
db_user=wordpress
db_password=password
db_name=wordpress
db_root_password=password
wp_debug_mode=false

Hello,
thank you for this great repo!
I'm rather new to docker / wordpress combo and I wonder if there is a mistake in the .env file.
In this section

####################################################
### Defaults - can be left as-is for basic usage ###
####################################################
db_host=db:3306
db_user=wordpress
db_password=password
db_name=wordpress
db_user=wordpress
db_password=password
db_root_password=password
wp_debug_mode=false

db_user and db_password are defined twice. Is this on purpose and if yes, what is the difference between these two? or is this a copy paste mistake?

On macbook pro M1 (Apple M1 Pro) with Ventura 13.4 .
I found this error that it's from compatibility of mysql with apple silicon chip.

Creating network "existing-wordpress-development-docker_default" with the default driver Pulling db (mysql:5.7)... 5.7: Pulling from library/mysql ERROR: no matching manifest for linux/arm64/v8 in the manifest list entries

Hey,
I'm facing another issue. I cannot get an existing environment to run with the script.

The scripts output is the following where it gets stuck. I'm starting the script in the folder "site.com"

xx@xxx-MacBook-Pro site.com % docker-compose up -d && docker-compose exec wordpress prep.sh Creating network "sitecom_default" with the default driver Creating sitecom_db_1 ... done Creating sitecom_wordpress_1 ... done No plugins to be disabled, skipping... Changing owner/group of wp-content recursively...

And then nothing happens.

I'm using an exported db from Plesk and the whole wp-content folder.
Plesk does not have a root password, maybe this is causing the issue?

I did not disable any plugins.

Any ideas whats happening here or how I could debug this?