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
Allowing multiple Exec= entries, like with Label=, would provide better readability and maintainability.
A prime example is the example docker-compose.yml of treafik with four long entries.
My own configuration is 18 arguments long and at exactly 1000 characters not easily manageable in a single line.
Suggest potential solution
Allowing multiple Exec= entries, like with Label=.
Have you considered any alternatives?
No. I am in the progress of migrating from docker compose and have not much experience with quadlets.
If there is an alternative approach, which I overlooked, please let me know.
I was able to start a container with multiple Exec= entries but podman ps shows only the arguments from the last entry.
This case, silently ignoring present configuration, seems more problematic than failing with an error.
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
1ab2d3e4f5g6 docker.io/library/traefik:latest --entryPoints.web... 7 minutes ago Up 7 minutes 80/tcp systemd-traefik
The text was updated successfully, but these errors were encountered:
Feature request description
Allowing multiple
Exec=
entries, like withLabel=
, would provide better readability and maintainability.A prime example is the example docker-compose.yml of treafik with four long entries.
My own configuration is 18 arguments long and at exactly 1000 characters not easily manageable in a single line.
Suggest potential solution
Allowing multiple
Exec=
entries, like withLabel=
.Have you considered any alternatives?
No. I am in the progress of migrating from docker compose and have not much experience with quadlets.
If there is an alternative approach, which I overlooked, please let me know.
Additional context
Related issue: #22027
I was able to start a container with multiple
Exec=
entries butpodman ps
shows only the arguments from the last entry.This case, silently ignoring present configuration, seems more problematic than failing with an error.
The text was updated successfully, but these errors were encountered: