search

azukaar / Cosmos-Server

☁️ The Most Secure and Easy Selfhosted Home Server. Take control of your data and privacy without sacrificing security and stability (Authentication, anti-DDOS, anti-bot)
https://cosmos-cloud.io
Other
2.97k stars 105 forks source link

[BUG]: When you delete volume other volumes became readonly #194

Closed TasyDevilsky closed 4 months ago

TasyDevilsky commented 4 months ago

What happened?

It's probably because of the update ability to edit docker-compose file. When you create any volume for container and after that delete it other volumes become read only.

image

What should have happened?

When I delete any volume, or bind storage from web interface it shouldn't affect other volumes.

How to reproduce the bug?

When you choose some container, especially Deluge for me and you try to attach another volume (from webUI Storage option), and after that you delete it, other volumes (config) and every else volume become read only, when you delete this line through WebUI docker-compose editor it will work, but when you repeat scenario (add volume, and after while delete it) it will become read only again.

Relevant log output

No relevant output

Other details

It affect also other containers, not only Deluge. No response

System details

azukaar commented 4 months ago

Fixed in 0.14.4 -- could you retest before I close the ticket please?

TasyDevilsky commented 4 months ago

Yeah it's fixed. PS: For everyone who is affected by this issue, you need to update to 0.14.4 and then just you will need to click on "Storage" in affected container and just click to "Update Volumes". I firstly tried to just delete it from docker-compose, but it didn't work.