If you wire up bad mounts, they stay there after the deploy fails #8

Closed
opened 2020-04-15 11:25:01 +00:00 by decentral1se · 1 comment
Owner

This means that you kinda bork your setup on the host side.

Not sure how that can be reversed from the client side.

Worth thinking about.

This means that you kinda bork your setup on the host side. Not sure how that can be reversed from the client side. Worth thinking about.
Author
Owner

You'd probably want some mechanism here to take a "snapshot" of the current storage mounted into the container before fucking with it. Because if you change it then you have to rebuild the container to get it working. So, you might bork your container later down the line when you deploy again.

You'd probably want some mechanism here to take a "snapshot" of the current storage mounted into the container before fucking with it. Because if you change it then you have to rebuild the container to get it working. So, you might bork your container later down the line when you deploy again.
This repo is archived. You cannot comment on issues.
No Label
No Milestone
No Assignees
1 Participants
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: autonomic-cooperative/dokku-ansible-deploy#8
No description provided.