Last active
May 10, 2016 08:45
-
-
Save termie/b641db3a4a44a8921de2e971ce124aed to your computer and use it in GitHub Desktop.
mostly able to run sysdig in a rkt container when your docker is hosed
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
image: using image from local store for image name coreos.com/rkt/stage1-fly:1.5.1 | |
image: using image from local store for url docker://sysdig/sysdig | |
* Setting up /usr/src links from host | |
ls: cannot access '/host/usr/src': No such file or directory | |
* Unloading sysdig-probe, if present | |
* Running dkms autoinstall | |
Kernel preparation unnecessary for this kernel. Skipping... | |
Building module: | |
cleaning build area.... | |
make KERNELRELEASE=4.4.6-coreos -C /lib/modules/4.4.6-coreos/build M=/var/lib/dkms/sysdig/0.9.0/build..... | |
cleaning build area.... | |
Kernel cleanup unnecessary for this kernel. Skipping... | |
DKMS: build completed. | |
sysdig-probe.ko: | |
Running module version sanity check. | |
- Original module | |
- No original module exists within this kernel | |
- Installation | |
- Installing to /lib/modules/4.4.6-coreos/kernel/extra/ | |
mkdir: cannot create directory '/lib/modules/4.4.6-coreos/kernel/extra': Read-only file system | |
cp: cannot create regular file '/lib/modules/4.4.6-coreos/kernel/extra/sysdig-probe.ko': No such file or directory | |
depmod.... | |
DKMS: install completed. | |
* Trying to load a system sysdig-probe, if present | |
* Trying to load a dkms sysdig-probe, if present | |
sysdig-probe found and loaded in dkms |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
#!/bin/sh | |
sudo rkt run --interactive docker://sysdig/sysdig \ | |
--insecure-options=image \ | |
--volume home,kind=host,source=/home/core,readOnly=false \ | |
--mount volume=home,target=/host/home \ | |
--volume docker,kind=host,source=/var/run/docker.sock,readOnly=false \ | |
--mount volume=docker,target=/host/var/run/docker.sock \ | |
--volume dev,kind=host,source=/dev,readOnly=false \ | |
--mount volume=dev,target=/host/dev \ | |
--volume proc,kind=host,source=/proc,readOnly=true \ | |
--mount volume=proc,target=/host/proc \ | |
--volume boot,kind=host,source=/boot,readOnly=true \ | |
--mount volume=boot,target=/host/boot \ | |
--volume modules,kind=host,source=/lib/modules,readOnly=true \ | |
--mount volume=modules,target=/host/lib/modules \ | |
--volume usr,kind=host,source=/usr,readOnly=true \ | |
--mount volume=usr,target=/host/usr \ | |
--stage1-name=coreos.com/rkt/stage1-fly:1.5.1 |
Did it open a shell after? Because all the errors there are fine, look the last line: sysdig-probe found and loaded in dkms
. On my system I was able to launch sysdig
and also csysdig
prepending the terminal var: TERM=xterm csysdig
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
(i'm not currently getting all of the sysdig output i want but this is also my first 10 minutes of ever touching the tool)