Replies: 6 comments
-
|
That's an interesting idea. I wonder how |
Beta Was this translation helpful? Give feedback.
-
|
Seem like |
Beta Was this translation helpful? Give feedback.
-
|
Cool, I did a small test with that: func newContainer(c docker.Summary, host string) container.Container {
name := c.Labels["com.docker.compose.service"]The result is exactly like the second picture above, i.e. perfect. I guess that will not be a value in all running containers, only those ran using docker compose. So it would need fallback. |
Beta Was this translation helpful? Give feedback.
-
|
That's right. But I think the logic needs to be in the UI and not backend. If a container is grouped under the stack name, then it should use service name. Which is a bit different. I'll keep this open until I can get to it. If you time a PR would be appreciated too. |
Beta Was this translation helpful? Give feedback.
-
|
Can you test #4358 with LMK. |
Beta Was this translation helpful? Give feedback.
-
|
Moving to discussion. People can upvote or suggest better options. Closed the PR as it turns out |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Describe the feature you would like to see
Dozzle beautifully groups containers by stack, but since my setup requires not setting explicit container names, all containers are listed with project name prefixed. This is not so beautiful.
Could there be an option to use the docker compose service names as display name instead of container name?
Describe how you would like to see this feature implemented
docker comopse -p <stackname> psreturns service name along with container name. There are probably other ways to get it with the API.In the UI there could be toggle for using this type of container display name.
Describe any alternatives you've considered
dev.dozzle.namelabels. This solves the problem! But requires manually setting labels for each container.Beta Was this translation helpful? Give feedback.
All reactions