Volume disconnected after redeploy for no (?) reason
I just triggered a redeploy after changing an environment variable for my service. Then the attached volume disconnected.
Rollback does not bring it back.
https://mauerwinzer.de/
Mauerwinzer
The wine bar with terrace and fireplace at the former Berlin Wall offering more than 180 different wines and sparkling wines from all 13 German growing regions.
Solution:Jump to solution
My bad, seems like the volume was not mounted from the start, it just looked like it was working. UI shows a size of 1.06 GB, even though it is empty?
16 Replies
Project ID:
1883e426-1079-4a91-bf0f-72969388a018project id: 1883e426-1079-4a91-bf0f-72969388a018
Solution
My bad, seems like the volume was not mounted from the start, it just looked like it was working. UI shows a size of 1.06 GB, even though it is empty?
you can attach the volume back to your service by clicking the mount button on the volume
I know, I used the term "disconnected" to say that the connection is not working. In the UI it was still attached.
and is 1.06GB the size of an empty volume?
no, you probably have something in it
hm, I added a new volume, mounted to a different path and it shows again exactly the same size
okay then that's normal I guess
it starts with 1.06GB
the Volume Inspector template also didn't show anything (if I used it correctly)
that would just be filesystem overhead
I think they should include just a tiny filebrowser in the UI, it's annoying not to know anything about the volume
this is filesystem overhead, there wouldn't be anything to see, but yes everyone agrees that a native filebrowser would be incredibly useful
I know! But if there was a filebrowser I would have connected the dots more quickly
to test if the persistence is working, I need to redeploy right? Or is restart enough?
either should work
ok, thank you!