Connection to dhcpcd lost at every boot [Solved]

[Xcraft]

Hi,

First, I'm sorry, I'm new to raspberry please bear with me and my desceiptions.

I migrated from an old laptop (as server via docker containers) to RPi 4. Installed Buster and everything is working fine. I went ahea dand installed 2 containers just to test out if my backup is working. I restarted and everything is working fine. After, I went ahead and install all my containers (14 of them) everything works great aside from some that doesn't have armfh support, figured that out after.

Then I rebooted. Network icon shows up&down with 2 X. Hovering to it, it shows "connection to dhcpcd lost" and "No wireless interface found". I can't ping the pi, I don't have Internet access. I use Ethernet BTW.

I searched for solutions and so far I tried:
1. Setting up Static IP at dhcpcd.conf
2. Editing my /etc/network/interfaces file and adding

Code: Select all

auth lo
iface lo inet dhcp

auth eth0
iface eth0 inet dhcp(and to manual)

3. I tried almost every solution I find in this forum and other sites but to no avail. Except the one relating to wpa_supplicant because I want to use Ethernet.

One solution that worked for me is executing the command:

Code: Select all

sudo dhcpcd - 4

It immediately connects me, and everything is working again. I disabled IPV6 via the interface as described from the thread (in this forum as well) where I found that command.

But the solution is not persistent. If I reboot I'm back to the problem.

Please help.

I noticed that there are new network interfaces with naming format as:

veth#####

There are 8 of them.

Please tell me what logs you need and how to acquire them. Thanks!

[epoch1970]

Maybe dhcpcd dies right after boot?
Docker creates various network devices for containers to run, perhaps dhcpcd gets confused by what's happening in the machine.

I would try reverting changes made to the interfaces file and all others, then add

Code: Select all

denyinterfaces veth*

to the beginning of /etc/dhcpcd.conf.
Then reboot and see.

[Xcraft]

Maybe dhcpcd dies right after boot?
Docker creates various network devices for containers to run, perhaps dhcpcd gets confused by what's happening in the machine.

I would try reverting changes made to the interfaces file and all others, then add

Code: Select all

denyinterfaces veth*

to the beginning of /etc/dhcpcd.conf.
Then reboot and see.

Thank you very much! I spent hours trying to solve this and that line is just magic! Everything is working as expected!

Edit: How do I mark the thread as solve?

[epoch1970]

You don't need to.
Some manage to edit the title in their initial post. I never do that so I'm not sure where to click.

( While I am here, one for the search engines: docker container network issue disconnected dhcpcd dhcpcd.conf denyinterfaces veth )

[FTrevorGowen]

You don't need to.
Some manage to edit the title in their initial post. I never do that so I'm not sure where to click.

( While I am here, one for the search engines: docker container network issue disconnected dhcpcd dhcpcd.conf denyinterfaces veth )

@epoch1970 w.r.t. "where to click" - the edit "pencil" symbol which is the first one of the group of symbols at the top right of the first post which formed the topic (for the default forum view).
@Xcraft on this occasion I've done it for you ...
Trev.