Open osmith42 opened 2 years ago
Hi!
Thanks for the PR. I had missed the original notification a few years back 😅
I'm a bit on the fence about that one, because if something goes wrong, the container is going to be removed, which will prevent looking at its logs, and will be annoying from a debugging perspective. What do you think?
Personally I think creating a container that does not get removed every time the script runs, is worse than that. I would suggest to rather redirect the log to a file for a better debugging experience. And maybe add a check that ensures udhcpc is actually running, and if it isn't, then print the log.
With that being said, I won't work on this pull request further, so feel free to merge or close it as you prefer :slightly_smiling_face:
Thanks for making pipework!
Use --rm with "docker run", so the remaining container does not consume disk space after the command is done.