Allow passing "EXCLUDE_CONTAINERS" and "EXCLUDE_IMAGES" as environmental vars about docker-gc HOT 5 CLOSED

@emmetog thanks for the detailed writeup. I can't see any reason why the "exclude container/image" logic couldn't be extended to give priority to an environment file before reading from the file (whose path can be overridden with an existing environment file already).

from docker-gc.

Hi @mattnworb, I'm not sure I understand your comment.

I can't see any reason why the "exclude container/image" logic couldn't be extended to give priority to an environment file before reading from the file (whose path can be overridden with an existing environment file already)

When you say "environment file" you mean an environment variable, right? Just in case there's a misunderstanding, I'm proposing environment variables, not files.

from docker-gc.

Right, I just mean that I can't see any reason to not implement this proposal 😄

from docker-gc.

and to be extra clear I would be happy to merge a PR that implemented this proposal

from docker-gc.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

from docker-gc.