Skip to content

Conversation

@thebsdbox
Copy link
Contributor

Description

The removes the bind mounts for DHCP

Why is this needed

Causes DHCP to fail with a pidlock error, with DHCP broken tink-worker can never start.

Fixes: #

How Has This Been Tested?

How are existing users impacted? What migration steps/scripts do we need?

Checklist:

I have:

  • updated the documentation and/or roadmap (if required)
  • added unit or e2e tests
  • provided instructions on how to upgrade

Signed-off-by: Dan Finneran <dan@thebsdbox.co.uk>
@mmlb
Copy link
Contributor

mmlb commented Sep 8, 2021

Does this cause resolv.conf to not be updated then?

@thebsdbox
Copy link
Contributor Author

@mmlb nope -> https://github.com/linuxkit/linuxkit/blob/master/pkg/dhcpcd/build.yml The dhcpd already has a /etc bind.

@tstromberg
Copy link
Contributor

Please give this PR a title that can be used for release notes. I first read the title and assumed this PR was about removing a DNS server.

@tstromberg tstromberg changed the title Removes bind Remove unnecessary bind mounts for linuxkit/dhcpcd Oct 5, 2021
@tstromberg tstromberg merged commit 5fc37b6 into tinkerbell:main Oct 5, 2021
mergify bot added a commit that referenced this pull request Apr 23, 2022
## Description


I was experiencing the same issue as [here](#79), 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:

- [ ] updated the documentation and/or roadmap (if required)
- [ ] added unit or e2e tests
- [ ] provided instructions on how to upgrade
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.

3 participants