package dependency

[Steini-]

hi,
i just wanted to setup a jool-container according the Readme-File, but it didn't went as smooth as expected.

The command line output from install.sh:
[...looked all fine so far but then...]

Jool-3.5.7/usr/stateless/
Jool-3.5.7/usr/stateless/.gitignore
Jool-3.5.7/usr/stateless/Makefile.am
Jool-3.5.7/usr/stateless/jool_siit.8
building and installing kernel module...

Creating symlink /var/lib/dkms/jool/3.5.7/source ->
                 /usr/src/jool-3.5.7

DKMS: add completed.

Kernel preparation unnecessary for this kernel.  Skipping...

Building module:
cleaning build area.....
make -j2 KERNELRELEASE=4.15.0-58-generic -C /lib/modules/4.15.0-58-generic/build SUBDIRS=/var/lib/dkms/jool/3.5.7/build/mod/stateful modules && make -C /lib/modules/4.15.0-58-generic/build SUBDIRS=/var/lib/dkms/jool/3.5.7/build/mod/stateless modules.........(bad exit status: 2)
ERROR (dkms apport): binary package for jool: 3.5.7 not found
Error! Bad return status for module build on kernel: 4.15.0-58-generic (x86_64)
Consult /var/lib/dkms/jool/3.5.7/build/make.log for more information.

Kernel preparation unnecessary for this kernel.  Skipping...

Building module:
cleaning build area....
make -j2 KERNELRELEASE=4.15.0-58-generic -C /lib/modules/4.15.0-58-generic/build SUBDIRS=/var/lib/dkms/jool/3.5.7/build/mod/stateful modules && make -C /lib/modules/4.15.0-58-generic/build SUBDIRS=/var/lib/dkms/jool/3.5.7/build/mod/stateless modules.......(bad exit status: 2)
ERROR (dkms apport): binary package for jool: 3.5.7 not found
Error! Bad return status for module build on kernel: 4.15.0-58-generic (x86_64)
Consult /var/lib/dkms/jool/3.5.7/build/make.log for more information.
modprobe: FATAL: Module jool not found in directory /lib/modules/4.15.0-58-generic
pulling docker container...
3.5.7: Pulling from jasperben/jool-docker
4fe2ade4980c: Pull complete 
369177fa017e: Pull complete 
d210619dbff2: Pull complete 
b26678ba3c16: Pull complete 
b34c6c4bf55b: Pull complete 
Digest: sha256:c6f64bc9ebe7b603074e677d222400f18af89a6135089980a04a48d653bc82e1
Status: Downloaded newer image for jasperben/jool-docker:3.5.7
docker.io/jasperben/jool-docker:3.5.7
clean up...
done!

So and after consulting the logfile, it tells this:
cat /var/lib/dkms/jool/3.5.7/build/make.log

DKMS make.log for jool-3.5.7 for kernel 4.15.0-58-generic (x86_64)
So 1. Sep 10:43:56 CEST 2019
make: Verzeichnis „/usr/src/linux-headers-4.15.0-58-generic“ wird betreten
Makefile:986: "Cannot use CONFIG_STACK_VALIDATION=y, please install libelf-dev, libelf-devel or elfutils-libelf-devel"
  CC [M]  /var/lib/dkms/jool/3.5.7/build/mod/stateful/pool4/empty.o
  CC [M]  /var/lib/dkms/jool/3.5.7/build/mod/stateful/pool4/db.o
  CC [M]  /var/lib/dkms/jool/3.5.7/build/mod/stateful/pool4/rfc6056.o
  CC [M]  /var/lib/dkms/jool/3.5.7/build/mod/stateful/bib/db.o
  CC [M]  /var/lib/dkms/jool/3.5.7/build/mod/stateful/bib/entry.o
  CC [M]  /var/lib/dkms/jool/3.5.7/build/mod/stateful/bib/pkt_queue.o
  CC [M]  /var/lib/dkms/jool/3.5.7/build/mod/stateful/timer.o

[....Well, i thought let's look for the packets, maybe i forgot something...]
[... sorry for the german errors messages. It says there are dependacy issues, and i was unable to resolve them...]

ffa-experiment@ffaexperiment ~ $ sudo apt-cache search libelf-dev
libelf-dev - libelf1 development libraries and header files
ffa-experiment@ffaexperiment ~ $ sudo apt-get install libelf-dev
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.       
Statusinformationen werden eingelesen.... Fertig
Einige Pakete konnten nicht installiert werden. Das kann bedeuten, dass
Sie eine unmögliche Situation angefordert haben oder, wenn Sie die
Unstable-Distribution verwenden, dass einige erforderliche Pakete noch
nicht erstellt wurden oder Incoming noch nicht verlassen haben.
Die folgenden Informationen helfen Ihnen vielleicht, die Situation zu lösen:

Die folgenden Pakete haben unerfüllte Abhängigkeiten:
 libelf-dev : Hängt ab von: libelf1 (= 0.165-3ubuntu1.2) aber 0.170-0.4ubuntu0.1 soll installiert werden
E: Probleme können nicht korrigiert werden, Sie haben zurückgehaltene defekte Pakete.

i don't know what do now? Any Ideas?

[Jasper-Ben]

This seems to be an issue with the Ubuntu installation on the host system. Can you please provide details on the installed Ubuntu version? Using the latest Ubuntu Docker image I can install libelf-dev without any problems.

[Jasper-Ben]

Semi-related: #4
Even if you manage to fix the dependency problem, you probably (depending on your used kernel) won't be able to install the kernel module v3.5.7.
A workaround might be to install the kernel module v4.0.5 but since I am unsure about its compatibility with the v3.5.7 user-space I would recommend waiting for v.4.0.5, which I am currently working on: #2

[Jasper-Ben]

Should work now with jool v4.0.5 in master branch

[Steini-]

well install.sh is running now smmothly. But starting up the docker container fails.
I didn't find any informations about how to do that, so i tried to figure it out by myself and tried (and failed):

sudo docker run -d --name jool jool-docker
Unable to find image 'jool-docker:latest' locally
docker: Error response from daemon: pull access denied for jool-docker, repository does not exist or may require 'docker login': denied: requested access to the resource is denied.

Any Ideas?

[Jasper-Ben]

the correct command from your example would be sudo docker run -d --name jool jasperben/jool-docker. However, you'd probably want to use docker-compose. Otherwise you'll have to add the options defined in docker-compose.yml to your docker run command (every time you start the docker container). Once you've installed docker-compose as described in the link above, starting the container in detached mode is as simple as running docker-compose up -d in the cloned directory. Stopping the container would be docker-compose down. Keep in mind, that the container will survive reboot, so you'll probably want to stop the container once you're done or change the line restart: unless-stopped to restart: no.

Side note on any potential issues once the container started: @christf wrote the actual jool config, so if you encounter any jool specific issues, please tag him as well (alongside myself). Currently he has more insight into jools internal workings.

[christf]

the docker-compose file references an image that does not exist on dockerhub. Keeping this open until resolution.

[Jasper-Ben]

the docker-compose file references an image that does not exist on dockerhub. Keeping this open until resolution.

Nope, the image on dockerhub exists, and it works as expected. Only the automatic build doesn't work atm:

docker pull jasperben/jool-docker
Using default tag: latest
latest: Pulling from jasperben/jool-docker
b8f262c62ec6: Pull complete 
4b454622fef5: Pull complete 
2574d405fee6: Pull complete 
32c37a1889d2: Pull complete 
Digest: sha256:6e85ca88a623aea13ff812f97157970143d2cf3c1b43f6b5f8e8a1a4b9573846
Status: Downloaded newer image for jasperben/jool-docker:latest
docker.io/jasperben/jool-docker:latest

[christf]

In that case I wonder why Download fails for OP and myself.

Can we please keep this Open until this has been sorted? It helps me with Notifications.

[Jasper-Ben]

In OPs case (at least the one mentioned here) he used the wrong image name (jool-docker instead of jasperben/jool-docker) as I mentioned above.

Regarding your issue: Can you paste the terminal output here? For me pulling the image works without any issues:

[jasper@arch-pc jool-docker]$ sudo docker-compose up -d
b8f262c62ec6: Pull complete
f5e76689b22e: Pull complete
c1d7edbbf146: Pull complete
051f0e816194: Pull complete
Digest: sha256:70de02eabe6701f64bc78125edc38613eaa79450c53ec4e6dcd90dc66f34d64e
Status: Downloaded newer image for jasperben/jool-docker:latest