Update dhcpcd onboot and service containers: #116
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
I was experiencing the same issue as here, but removing all the bind mounts didn't resolve it for me. However, adding the bind mounts back and creating the
/var/lib/dhcpcd
directory was the only way for me to get the interfaces to start working. With these changes the dhcpcd.log files were error free.Hey @thebsdbox. If you have any cycles, I'd be very interested to know if the
main: pidfile_lock: Permission denied
error still happens for you with this PR.Update dhcpcd onboot and service containers:
Network interfaces were not coming up. Logs showed "
main: pidfile_lock: Permission denied
". Adding the bind mounts and directory creation resolved the issue.Why is this needed
Fixes: #
How Has This Been Tested?
How are existing users impacted? What migration steps/scripts do we need?
Checklist:
I have: