-
Steps to reproduce
all-in-one/php/containers.json Lines 73 to 75 in 267aebf Expected behaviorActual behaviorOther informationHost OSOutput of
|
Beta Was this translation helpful? Give feedback.
Replies: 11 comments 7 replies
-
Maybe this behavior is intended for yaml, but it's confusing. |
Beta Was this translation helpful? Give feedback.
-
Yes, it is intended because we generate https://github.com/nextcloud/all-in-one/blob/main/manual-install/latest.yml and https://github.com/nextcloud/all-in-one/tree/main/nextcloud-aio-helm-chart out of it. Do you have a better idea how to do that? |
Beta Was this translation helpful? Give feedback.
-
Why have a cap_drop in YAML, but not with the mastercontainer ? |
Beta Was this translation helpful? Give feedback.
-
Because cap_drop is by default applied for all containers: |
Beta Was this translation helpful? Give feedback.
-
Or WDYM? |
Beta Was this translation helpful? Give feedback.
-
Linking to #3377 which was introduced first. Later #4116 was created. |
Beta Was this translation helpful? Give feedback.
-
Actually, all of them are only there for the docker-compose yaml and the helm chart because they are generated out of the containers.json. In the mastercontainer itself is a separate logic to handle these, thus they are not actually needed for the mastercontainer. How should we proceed with this issue? |
Beta Was this translation helpful? Give feedback.
-
Move this to discussions as ideas? |
Beta Was this translation helpful? Give feedback.
-
Sounds good 👍 |
Beta Was this translation helpful? Give feedback.
-
I found this which is not used: all-in-one/php/src/Auth/AuthManager.php Line 30 in 9341392 |
Beta Was this translation helpful? Give feedback.
-
This files is nevr read: all-in-one/php/src/Auth/AuthManager.php Line 37 in 9341392 |
Beta Was this translation helpful? Give feedback.
cap_drop
,profiles
,user
,networks
orexpose
Actually, all of them are only there for the docker-compose yaml and the helm chart because they are generated out of the containers.json. In the mastercontainer itself is a separate logic to handle these, thus they are not actually needed for the mastercontainer.
How should we proceed with this issue?