Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ipdk connect not working #271

Open
drobinkent opened this issue Oct 15, 2022 · 3 comments
Open

ipdk connect not working #271

drobinkent opened this issue Oct 15, 2022 · 3 comments

Comments

@drobinkent
Copy link

I am trying to use the networking build with containerized version. I am following the steps described in

My host machine is running Ubuntu 22.04.

After the vagrant is up when I try to execute the following command

ipdk connect
It gives the following output.

vagrant@ubuntu2004:$ ipdk connect
-bash: ipdk: command not found
vagrant@ubuntu2004:
$

Can someone please guide me a bit here.

@jokuniew
Copy link
Contributor

When you do vagrant up and vagrant ssh to your machine
Go to cd /git/ipdk since this is synced folder as you can see in Vagrantfile

Then run ./build/ipdk -install <your OS of choice>
you should see the message

As last step execute:
  export PATH=/git/ipdk/build:$PATH
to add the IPDK CLI to your path in the running environment!

When you do export PATH=/git/ipdk/build:$PATH you'll resolve ipdk: command not found problem

To connect to ipdk, first you need to launch ipdk container, so:
ipdk start -d (-d for daemon)
And finally ipdk connect

@jokuniew
Copy link
Contributor

jokuniew commented Nov 9, 2022

@jafingerhut i've seen in your README that you've mentioned it as well (Follow instructions in file build/networking/README_DOCKER.md, under heading "Login to the VM":)

@mestery @dandaly what about extending provision.sh with export PATH=/git/ipdk/build:$PATH >> /etc/profile or some .bashrc? so the ipdk command will be available out of the box on vagrant's VM?

@jfingerh
Copy link

jfingerh commented Nov 9, 2022

Anything that can be added to the README steps for installation that makes them work for more people, more completely, without any missing steps that they have to figure out on their own, or search through Github issues to find out, is a good thing, in my opinion. Why make people who want to use your software solve puzzles, when you can give them working complete instructions?

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

No branches or pull requests

3 participants