Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

I have the following docker configuration for Mautic (A PHP based CRM):
x-mautic-volumes:
&mautic-volumes
- ./mautic/config:/var/www/html/config:z
- ./mautic/logs:/var/www/html/var/logs:z
- ./mautic/media/files:/var/www/html/docroot/media/files:z
- ./mautic/media/images:/var/www/html/docroot/media/images:z
- ./mautic/themes/leeway_newsletter:/var/www/html/docroot/themes/leeway_newsletter:z
- ./mautic/themes/leeway_responsive:/var/www/html/docroot/themes/leeway_responsive:z
- ./session.ini:/usr/local/etc/php/conf.d/session.ini:z
- ./cron:/opt/mautic/cron:z
- mautic-docroot:/var/www/html/docroot:z
- mautic-vendor:/var/www/html/vendor:z
services:
nginx:
image: nginx
volumes:
- ./nginx.conf:/etc/nginx/conf.d/default.conf
- mautic-docroot:/var/www/html/docroot:z
- ./mautic/media/files:/var/www/html/docroot/media/files:z
- ./mautic/media/images:/var/www/html/docroot/media/images:z
- ./.well-known:/var/www/html/docroot/.well-known
depends_on:
- web
ports:
- "127.0.0.1:8002:80"
networks:
- default
restart: always
web:
image: my_mautic:5.2.1
build: .
volumes: *mautic-volumes
env_file:
- .mautic_env
healthcheck:
test: cgi-fcgi -bind -connect 127.0.0.1:9000
start_period: 5s
interval: 5s
timeout: 5s
retries: 100
networks:
- default
restart: always
cron:
image: my_mautic:5.2.1
build: .
volumes: *mautic-volumes
environment:
- DOCKER_MAUTIC_ROLE=mautic_cron
env_file:
- .mautic_env
depends_on:
web:
condition: service_healthy
networks:
- default
restart: always
volumes:
mautic-docroot:
name: mautic-5.2.1
mautic-vendor:
name: mautic-5.2.1-vendor
networks:
default:
name: ${COMPOSE_PROJECT_NAME}-docker
This application is accessed through an NginX that takes care of SSL and forwards traffic to both this docker container and a regular WordPress hosted directly on the server using php8.2-fpm.
I have my servers on Basic Premium Intel droplets (1 GB Ram, 1vCPU, 25GB disk).
The app is currently running just fine on an Ubuntu 23.10 server.
I tried to put together a new server using Ubuntu 24.04 and, using the exact same configuration, after running for about 20 minutes, the CPU usage will go to 100% and stay there until I manually kill the in-docker php-fpm process.
I tried installing docker from the official sources, re-install the whole thing from scratch to make sure I wasn’t using old volumes, explicitly limited resources for the web container but I always end up in the same place.
Any idea?
Thanks!
d1dd3d9538cc4d06b53e6d1d338d3f
50ff4e4b3c6c4999a12403b1ecda95
a6309a057c3f4cb38fb2e7feb67236
72e571841e7f4a6881090a2f3e93c0
57a72a98162f46a5a5cd04d9b
Thomas Brocken
11575c6d695643cdb40ad47d0f1aea
tez.saad
keneucker
keneucker
max johnson
max johnson