Create a docker-compose file with multiple services mounting the same volume. Convert it.
Expected behavior
Only one persistent volume claim should be created with ReadWriteMany attribute set.
Faulty behavior
One persistent volume claim is created for each service. Services don't share the same data as the docker setup would expect.
### Version
3, develop branch
### Reproduce
Create a docker-compose file with multiple services mounting the same volume. Convert it.
### Expected behavior
Only one persistent volume claim should be created with ReadWriteMany attribute set.
### Faulty behavior
One persistent volume claim is created for each service. Services don't share the same data as the docker setup would expect.
I will probably change the way I manage named volumes to create "global" volume claims and to allow mapping the volume on all deployments
OK, right. I confirm this is a bug.
I will probably change the way I manage named volumes to create "global" volume claims and to allow mapping the volume on all deployments
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Version
3, develop branch
Reproduce
Create a docker-compose file with multiple services mounting the same volume. Convert it.
Expected behavior
Only one persistent volume claim should be created with ReadWriteMany attribute set.
Faulty behavior
One persistent volume claim is created for each service. Services don't share the same data as the docker setup would expect.
Ho, I will test this. Sorry for the delay
OK, right. I confirm this is a bug.
I will probably change the way I manage named volumes to create "global" volume claims and to allow mapping the volume on all deployments
I just ran into this issue too.