Katenary/katenary
2
0
Fork 0
Code Issues 7 Pull Requests Actions Packages Projects Releases 15 Wiki Activity

Bug: Persistent volume creation #75

New Issue
Open
opened 2024-08-14 08:44:36 +00:00 by unicode-it · 3 comments
unicode-it commented 2024-08-14 08:44:36 +00:00 (Migrated from github.com)
Copy Link

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.

### 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.
metal3d commented 2024-10-29 17:08:46 +00:00
Copy Link

Ho, I will test this. Sorry for the delay

Ho, I will test this. Sorry for the delay
metal3d commented 2024-10-29 17:19:21 +00:00
Copy Link

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

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
jpsnyder commented 2025-07-03 21:06:20 +00:00 (Migrated from github.com)
Copy Link

I just ran into this issue too.

I just ran into this issue too.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Something isn't working
dependencies
Pull requests that update a dependency file
documentation
Improvements or additions to documentation
duplicate
This issue or pull request already exists
enhancement
New feature or request
go
Pull requests that update go code
good first issue
Good for newcomers
help wanted
Extra attention is needed
invalid
This doesn't seem right
partially fixed
Some fixes are already made in current release / developpement
question
Further information is requested
wontfix
This will not be worked on
No Label
bug
Milestone
No items
No Milestone v3.0.1
Projects
Clear projects
No project
Assignees
Clear assignees
metal3d
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Katenary/katenary#75
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?