Hello Claus,
Thank you very much, i already compiled vtuner module by changing the path in Makefile.
The funny thing is after i did all that i noticed that vtuner is already included in MLD 5.3.5 kernel sources
root@92bafaf276d7:/MLD/kernel/src/linux-5.3.5/drivers/media/vtuner# ls
Kconfig vtunerc.ko vtunerc.o vtunerc_main.o
Makefile vtunerc.mod vtunerc_ctrldev.c vtunerc_priv.h
modules.order vtunerc.mod.c vtunerc_ctrldev.o vtunerc_proxyfe.c
vtuner.h vtunerc.mod.o vtunerc_main.c vtunerc_proxyfe.o
So why you don't make it available for download in MLD 5.4 testing branch?
MLD> apt search vtuner
Sorting... Done
Full Text Search... Done
I think docker containers are similar to virtual machines in windows, i'm still learning about it though.
For ex.,
MLD> docker images -a
REPOSITORY TAG IMAGE ID CREATED SIZE
mld/devel 5.4 cd043bf25c68 2 days ago 967MB
<none> <none> 01e85ee1f011 2 days ago 582MB
<none> <none> 220f8b9d5448 2 days ago 539MB
<none> <none> da6238eec7e8 2 days ago 101MB
<none> <none> 28e0fb4d2e31 2 days ago 101MB
debian stretch 4f5edfdf153f 6 days ago 101MB
MLD> docker rmi 01e85ee1f011
Error response from daemon: conflict: unable to delete 01e85ee1f011 (cannot be forced) - image has dependent child images
I don't know what are those images with <none> tag which i'm unable to delete
Any idea?
I was playing around then installed an image called dperson/samba then deleted it so it's not one of those images.
Secondly,
docker network inspect bridge
"IPv4Address": "172.17.0.2/16",
What i can do with the container ip address?