Will be good to put clean of files inside /tmp/sysdig-agent* after install else other users will not be able to install
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 35/100
Research direction
Start with sysdig-install-agent-k8.sh and inspect how it creates the /tmp/sysdig-agent-clusterrole.yaml, /tmp/sysdig-agent-daemonset-v2.yaml, and /tmp/sysdig-agent-configmap.yaml files. Reproduce the installation with two users and verify that a second user can install successfully after the first installation, with no blocking leftover files.
Written by the indexing model from the issue text.
Description
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.
- Dominant language
- Shell
- Stars
- 83
- Forks
- 105
- Avg merge
- 3h 53m
- Merged PRs (30d)
- 1
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from draios/sysdig-cloud-scripts
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
draios/sysdig-cloud-scripts#248 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 20/100
draios/sysdig-cloud-scripts#176 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 15/100
draios/sysdig-cloud-scripts#124 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
draios/sysdig-cloud-scripts#110 · 7 comments ·
-
Sysdig Agent Limits? Open
Difficulty 4/5 3-5 days Newbie friendliness 25/100
draios/sysdig-cloud-scripts#106 ·
All issues in draios/sysdig-cloud-scripts
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
danielmiessler/LifeOS#2218 ·
-
docs(agents): strengthen the no-backslash-escaped-backticks rule with an issue-creation example Open
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
package-update
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
oSoWoSo/vOid_Community_repOsitory#148 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
chore
Difficulty 1/5 Under an hour Newbie friendliness 91/100
alunduil/alunduil-chezmoi#792 ·