phoenix-media / magento2-cloud-build Goto Github PK

Hi, when i run the docker compose up, the architecture run and http:///localhost response correctly.

the problem is thati receive an exception

usually i receive this error on another infrastructure when permission are not setted correctly.

Hi! i'm trying to follow your guide for deploying the infrastructure.
First try: Deploying existing m2
The first try was building a docker image based on the current development that we have done.
The infrastructure already exist with his environment but when we build the image we always receive error connection with redis or mysql.
It looks like that the services are not comunicating each other.

Second try: magento-from scratch

there are some changes that i needed to make:

cloud build

composer require phoenix-media/magento2-cloud-build --no-update

became

composer require phoenix-media/magento2-cloud-build:1.0.29 --no-update

for downloading the latest version that is compatble with magento 2.4.5

then we try to run

docker build . -t xx/yy

and then

docker compose up

rabbit and redis looks running but magento return this log:

agento | ****************************** magento | ** nginx server_name SETUP *** magento | ****************************** magento | ****************************** magento | ******* POSTFIX SETUP ******** magento | ****************************** magento | ****************************** magento | ******* PHP SETUP ************ magento | ****************************** magento | 2024-01-10 04:03:53,753 CRIT Supervisor is running as root. Privileges were not dropped because no user is specified in the config file. If you intend to run as root, you can set user=root in the config file to avoid this message. magento | 2024-01-10 04:03:53,754 INFO supervisord started with pid 1 magento | 2024-01-10 04:03:54,759 INFO spawned: 'deploy' with pid 8 magento | 2024-01-10 04:03:54,761 INFO spawned: 'nginx' with pid 9 magento | 2024-01-10 04:03:54,762 INFO spawned: 'php-fpm' with pid 10 magento | 2024-01-10 04:03:54,764 INFO spawned: 'master' with pid 11 magento | /bin/bash: line 1: /var/www/html/bin/deploy: No such file or directory magento | 2024-01-10 04:03:54,764 INFO success: deploy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) magento | 2024-01-10 04:03:54,764 INFO success: master entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) magento | 2024-01-10 04:03:54,764 INFO exited: deploy (exit status 127; not expected) magento | 2024/01/10 04:03:54 [emerg] 9#9: "server_names_hash_bucket_size" directive is not allowed here in /etc/nginx/conf.d/healthz.conf:1 magento | nginx: [emerg] "server_names_hash_bucket_size" directive is not allowed here in /etc/nginx/conf.d/healthz.conf:1 magento | 2024-01-10 04:03:54,773 INFO exited: nginx (exit status 1; not expected) magento | [10-Jan-2024 04:03:54] NOTICE: fpm is running, pid 10 magento | [10-Jan-2024 04:03:54] NOTICE: ready to handle connections magento | 2024-01-10 04:03:54,892 INFO exited: master (exit status 0; expected) magento | 2024-01-10 04:03:55,894 INFO spawned: 'nginx' with pid 93 magento | 2024-01-10 04:03:55,895 INFO success: php-fpm entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) magento | 2024/01/10 04:03:55 [emerg] 93#93: "server_names_hash_bucket_size" directive is not allowed here in /etc/nginx/conf.d/healthz.conf:1 magento | nginx: [emerg] "server_names_hash_bucket_size" directive is not allowed here in /etc/nginx/conf.d/healthz.conf:1 magento | 2024-01-10 04:03:55,914 INFO exited: nginx (exit status 1; not expected) magento | 2024-01-10 04:03:57,920 INFO spawned: 'nginx' with pid 94 magento | 2024/01/10 04:03:57 [emerg] 94#94: "server_names_hash_bucket_size" directive is not allowed here in /etc/nginx/conf.d/healthz.conf:1 magento | nginx: [emerg] "server_names_hash_bucket_size" directive is not allowed here in /etc/nginx/conf.d/healthz.conf:1 magento | 2024-01-10 04:03:57,927 INFO exited: nginx (exit status 1; not expected) magento | 2024-01-10 04:04:00,934 INFO spawned: 'nginx' with pid 95 magento | 2024/01/10 04:04:00 [emerg] 95#95: "server_names_hash_bucket_size" directive is not allowed here in /etc/nginx/conf.d/healthz.conf:1 magento | nginx: [emerg] "server_names_hash_bucket_size" directive is not allowed here in /etc/nginx/conf.d/healthz.conf:1 magento | 2024-01-10 04:04:00,945 INFO exited: nginx (exit status 1; not expected) magento | 2024-01-10 04:04:01,946 INFO gave up: nginx entered FATAL state, too many start retries too quickly
it looks like that nginx is failing becose the default conf file is not working.

I created a repo for checking the status

link

Hi there, after the building of the docker image it generate the env.php file on the fly.
The problem is that inside the env is inserting

web/unsecure/base_url
web/secure/base_url

and the values are my local environment.

i dont know where it'ts getting this value because it's not saved anywhere in the code (no config, no env)

so when we deploy the chart to helm, this value is not overridden by the MAGENTO_ROUTES base64 encode.

logging to the db is always returning the local env.

Hi,

I tried pulling your Docker image phoenixmedia/magento2:2.4.5

But I do not get Agree & Continue not coming.

Hi bjoern

I currently receive an issue when i try to build the default phoenix media magento 2 image
The build says it can not copy config.php last line:

  - Installing phoenix-media/magento2-cloud-build (1.0.28): Extracting archive
  0/19 [>---------------------------]   0%
  6/19 [========>-------------------]  31%
  8/19 [===========>----------------]  42%
 11/19 [================>-----------]  57%
 16/19 [=======================>----]  84%
 19/19 [============================] 100%
3 package suggestions were added by new dependencies, use `composer suggest` to see details.
Package symfony/debug is abandoned, you should avoid using it. Use symfony/error-handler instead.
Package php-cs-fixer/diff is abandoned, you should avoid using it. No replacement was suggested.
Generating autoload files
129 packages you are using are looking for funding.
Use the `composer fund` command to find out more!
cp: can't stat 'vendor/phoenix-media/magento2-cloud-build/dist/config.php': No such file or directory

I believe its the cd ${INSTALL_DIR} from the current change thats causing this error, because in the install dir there is no direct vendor directory as child, could this be ? Maybe im wrong.