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
Describe the bug
Hi
When I launch 2 workflows at the same time that use service container (to run postgres, redis an rabbitmq for example), they have the same label.
As you can see, the 1st workflow creates a network with this label :
Create local container network
/usr/bin/docker network create --label c3f261 github_network_02a5eecd05de4c4f
But the second one is going to destroy the first :
Clean up resources from previous jobs
/usr/bin/docker ps --all --quiet --no-trunc --filter "label=c3f261"
/usr/bin/docker network prune --force --filter "label=c3f261"
Deleted Networks:
github_network_02a5eecd05de4c4f
To Reproduce
Steps to reproduce the behavior:
In my case, when I launch two workflows at the same time, the second one always destroy the first
Expected behavior
How to modify this label so the workflows can be no dependant ?
Runner Version and Platform
My runners are currently hosted on an ECS cluster
What's not working?
The first job :
The second job that destroys the first one :
The text was updated successfully, but these errors were encountered:
Can you explain how did you start your runners, so I can reproduce this issue exactly ☺️? I think I know where the fix should be applied to, but I want to confirm that I'm covering your use-case
Can you explain how did you start your runners, so I can reproduce this issue exactly ☺️? I think I know where the fix should be applied to, but I want to confirm that I'm covering your use-case
Yes for sure ! They are manually triggered with dispatch mode! :
Describe the bug
Hi
When I launch 2 workflows at the same time that use service container (to run postgres, redis an rabbitmq for example), they have the same label.
As you can see, the 1st workflow creates a network with this label :
But the second one is going to destroy the first :
To Reproduce
Steps to reproduce the behavior:
Expected behavior
How to modify this label so the workflows can be no dependant ?
Runner Version and Platform
My runners are currently hosted on an ECS cluster
What's not working?
The first job :
The second job that destroys the first one :
The text was updated successfully, but these errors were encountered: