You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We would like to run our integration (nri-ecs) on ECS EC2 having cgroupsV2, however, due to the change of the value of default-cgroupns-mode for cgourpsV2 (with moby/moby#40174) we have some issues since we cannot access some files we leverage to gather and compute several metrics.
I think it is already possible to modify the default-cgroupns-mode therefore I do not expect that to be a security issue, just a missing flag. Consider that it was an issue other projects had compose-spec/compose-spec#148.
Expected Behavior
I'd like to have the possibility to configure from the task --cgroupns to override the default?
Is there a workaround to set such option per task?
The text was updated successfully, but these errors were encountered:
Summary
We would like to be able to leverage the Docker "--cgroupns" flag when creating a task.
Why
We would like to run our integration (nri-ecs) on ECS EC2 having cgroupsV2, however, due to the change of the value of
default-cgroupns-mode
for cgourpsV2 (with moby/moby#40174) we have some issues since we cannot access some files we leverage to gather and compute several metrics.I think it is already possible to modify the
default-cgroupns-mode
therefore I do not expect that to be a security issue, just a missing flag. Consider that it was an issue other projects had compose-spec/compose-spec#148.Expected Behavior
--cgroupns
to override the default?The text was updated successfully, but these errors were encountered: