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

Will be good to put clean of files inside /tmp/sysdig-agent* after install else other users will not be able to install #73

Open
niteenkole opened this issue Jul 5, 2019 · 0 comments

Comments

@niteenkole
Copy link

niteenkole commented Jul 5, 2019

As different user on same system,it fails without any error.Looks like as say user coopnonprod-tor01 on system infosec it create below files owned by coopnonprod-tor01

coopnonprod-tor01@infosec:/tmp$ ls -lart
-rw-rw-r-- 1 coopnonprod-tor01 coopnonprod-tor01 836 Jul 5 16:42 sysdig-agent-clusterrole.yaml
-rw-rw-r-- 1 coopnonprod-tor01 coopnonprod-tor01 3107 Jul 5 16:42 sysdig-agent-daemonset-v2.yaml
-rw-rw-r-- 1 coopnonprod-tor01 coopnonprod-tor01 1282 Jul 5 16:42 sysdig-agent-configmap.yaml

Now from same system infosec I want to install sysdig agent from say different user coopnonprod-mon01 to different cluster,it just fails

coopnonprod-mon01@infosec:~/sysdig$ ./sysdig-install-agent-k8.sh -a 32d84351-a7e7-46xxxxxxx -c ingest.us-south.monitoring.cloud.ibm.com -ac 'sysdig_capture_enabled: true'

  • Detecting operating system
  • Downloading Sysdig cluster role yaml ---No errors and stops here
    coopnonprod-mon01@infosec:~/sysdig$

Looks like after install need to clean up files /tmp/sysdig-agent* which are owned by previous user.

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

1 participant