Issue with netopeer2-cli connect command

[anoikob]

Hello again. I have a windows 11 machine. In this machine, I have an ubuntu 22.04 LTS VM. Inside the VM, I have installed docker engine CE 28.0.4, and I'm running a netopeer container, specifically this one . Before I installed docker CE, I had docker desktop installed for linux. In that instance, the netopeer2-cli command connect netconf@localhost --port 830 --login netconf would work fine, and I could interact with the datastores through get-config and other such commands. Now however, with Docker Engine CE installed, whenever I try to connect with that command I get a "connection refused" error. Bear in mind that I took extra care to delete every trace of docker desktop so that it doesn't interfere with docker CE.

So far I've tried:

1. Checking for processes inside the container that use the port 830
   

2. The same for the entire VM
   

3. The same for the host machine, the windows 11 pc

According to these results, nothing is using port 830. What could be the issue here? Is it a docker CE thing? Before someone asks, I chose to replace docker desktop with docker ce because I wanted to enable networking, and more specifically, i wanted the host machine (linux vm) to be able to ping the container.

[michalvasko]

So is netopeer2-server even running?

[anoikob]

Should it not be? I never had to manually start the server, I would just always automatically connect with the aforementioned command. I would always just type netopeer2-cli, then connect with the command, I never had to initialize the server myself.

[michalvasko]

That is a really old sysrepo version used in the image but fine. I am not using these images myself so I cannot help you but I would look at some service output of netopeer2, it is either not running or had some problem binding to the listening address/port.

[anoikob]

Ok I solved the issue. Turns out, this time, I had to manually start the server. I used the command /usr/sbin/netopeer2-server -d -v2 so I could see the logs. The logs indicated that everything was fine. I exec'd into the container from another terminal, used netopeer2-cli to connect to the server and everything is ok again.