rm doesn't clean up config #577

Open
opened 2025-06-18 22:29:16 +00:00 by ammaratef45 · 2 comments
Member

I've created an app using abra app new .. then removed it using abra app rm ... but docker config ls on the server shows the configs from this app are not cleaned up

I've created an app using `abra app new ..` then removed it using `abra app rm ...` but `docker config ls` on the server shows the configs from this app are not cleaned up
ammaratef45 added the
bug
label 2025-06-18 22:29:16 +00:00
Author
Member

One thing that could be the reason, the recipe had a config during the creation that wasn't there during the cleanup, perhaps some sort of an error silently happened during the rm process

One thing that could be the reason, the recipe had a config during the creation that wasn't there during the cleanup, perhaps some sort of an error silently happened during the rm process
Owner

I believe the compose configs are merged to discover configs/secrets/etc. and then things are deleted. So, if you change your config, yes, you can disrupt what will be deleted. We could implement a more thorough cleanup searching for configs/secrets/volumes/etc. matching the convention? I'm not sure if this would have unintended consequences.

I believe the compose configs are merged to discover configs/secrets/etc. and then things are deleted. So, if you change your config, yes, you can disrupt what will be deleted. We could implement a more thorough cleanup searching for configs/secrets/volumes/etc. matching the convention? I'm not sure if this would have unintended consequences.
decentral1se self-assigned this 2025-07-08 09:58:43 +00:00
decentral1se added the
red abya yala
label 2025-07-08 10:02:24 +00:00
decentral1se added this to the Abra "next" project 2025-07-08 10:06:51 +00:00
Sign in to join this conversation.
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: toolshed/abra#577
No description provided.