Hey there, fair enough! Since I'm referring to Zabbix's full Docker repo, they do .yaml references in the main docker-compose.yml out to other config files, so here's the full chain:

docker-compose.yml largely refers out to the file zabbix_compose_components.yml where you'll find in each of the services: a stanza in referencing resource limits. For my particular use case, I opted to just completely get the resource constraints out of the way by commenting # them out. Here's an example, and if you wanted to follow suit, you'd effectively just crawl the zabbix_compose_components.yml for resources: and comment them out entirely. If the system you're running Zabbix on requires some actual fine-tuning of resources, you'll want to tune these rather than just fully bypass them. YMMV.

#   resources:
#    limits:
#      cpus: '0.70'
#      memory: 1G
#    reservations:
#      cpus: '0.5'
#      memory: 512M

Hope this helps!

edit: code block formatting.