dlen
commented
4 months ago Hey there!
Ipv6 is a nginx config, mounting a nginx custom configuration file in /etc/nginx/sites-enabled/nginx-passbolt.conf will solve your issue. You can leverage the extraVolumeMounts in your values file.
The Passbolt app pod is crash-looping due to the Nginx configuration enabling IPv6, even though IPv6 is disabled in our environment. Our deployments are managed via ArgoCD using this Helm chart. I am seeking guidance on removing the IPv6 enablement, either through values.yaml or other automated methods, to avoid manual changes to the deployment.
ngsai-passbolt-depl-srv self.warnings.warn( │ │ ngsai-passbolt-depl-srv 2024-03-06 13:47:18,496 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 messag │ │ ngsai-passbolt-depl-srv 2024-03-06 13:47:18,496 INFO Included extra file "/etc/supervisor/conf.d/cron.conf" during parsing │ │ ngsai-passbolt-depl-srv 2024-03-06 13:47:18,496 INFO Included extra file "/etc/supervisor/conf.d/nginx.conf" during parsing │ │ ngsai-passbolt-depl-srv 2024-03-06 13:47:18,496 INFO Included extra file "/etc/supervisor/conf.d/php.conf" during parsing │ │ ngsai-passbolt-depl-srv 2024-03-06 13:47:18,499 INFO RPC interface 'supervisor' initialized │ │ ngsai-passbolt-depl-srv 2024-03-06 13:47:18,499 CRIT Server 'unix_http_server' running without any HTTP authentication checking │ │ ngsai-passbolt-depl-srv 2024-03-06 13:47:18,499 INFO supervisord started with pid 1 │ │ ngsai-passbolt-depl-srv 2024-03-06 13:47:19,502 INFO spawned: 'php-fpm' with pid 179 │ │ ngsai-passbolt-depl-srv 2024-03-06 13:47:19,505 INFO spawned: 'nginx' with pid 180 │ │ ngsai-passbolt-depl-srv nginx: [emerg] socket() :80 failed (97: Address family not supported by protocol) │ │ ngsai-passbolt-depl-srv 2024-03-06 13:47:19,530 WARN exited: nginx (exit status 1; not expected)