Summary
The user is facing issues running Airbyte in a Docker container due to CPU/Memory limits and cgroup issues. The Docker image creation for source/destination connectors includes specific flags that require kernel permissions.
Question
hello, has anyone overcame the issue running airbyte in a docker container where the following cpu/memory limits fail due to cgroup issues? It seems the docker image creation for source/destination connectors includes the following flags:
–cpus=1 --memory-reservation=1Gi --memory=2Gi
and this requires kernel permissions. surely someone has come across this !
This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.