Skip to content

Checking containers on first run + cleanup#14

Open
michaelfarrow wants to merge 1 commit into
allfro:masterfrom
michaelfarrow:feature/check-on-first-run
Open

Checking containers on first run + cleanup#14
michaelfarrow wants to merge 1 commit into
allfro:masterfrom
michaelfarrow:feature/check-on-first-run

Conversation

@michaelfarrow
Copy link
Copy Markdown

If this image is run after other stacks / containers, it won't fix the required devices as it only listens for newly running containers. This is likely to happen if restarting a swarm host.

This change adds an initial check of all running containers on first run.

Also cleaned up import order.

PS. My first time using go, sorry for any mistakes 😬

@michaelfarrow michaelfarrow force-pushed the feature/check-on-first-run branch 2 times, most recently from 6e19505 to a99ab6a Compare January 13, 2024 23:52
@michaelfarrow michaelfarrow force-pushed the feature/check-on-first-run branch from a99ab6a to 294ef6d Compare January 13, 2024 23:54
@mels0n
Copy link
Copy Markdown

mels0n commented Mar 24, 2024

@allfro - This appears to solve a use case I've run into. Are you open to merging?

@davehope
Copy link
Copy Markdown

@allfro This seems to be working really well, albeit for this issue which Michael has kindly submitted a PR for. Is there anything further needed that's preventing it being merged?

Thanks!

@fma965
Copy link
Copy Markdown

fma965 commented Jul 24, 2024

@michaelfarrow as this doesn't seem to be being merged, could you post your fork to dockerhub or ghcr for ease of access

@michaelfarrow
Copy link
Copy Markdown
Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants