cloud-native-toolkit / cloud-native-toolkit/multi-tenancy-gitops
Permission issue in bootstrap.sh when running set-git-source.sh from newly created gitops-0-bootstrap folder
- Langage dominant
- Shell
- Étoiles
- 120
- Forks
- 713
- Métriques de merge des PR
- Aucune PR mergée en 30 j
Description
When trying to run bootstrap.sh in a docker container (image registry.access.redhat.com/ubi8/python-39) I receive a "Permission denied" error when it reaches the set_git_source function and tries to run `GIT_ORG=${GIT_ORG} ./scripts/set-git-source.sh`.
I looked into it, and it appears that when the gitops-0-bootstrap repo is cloned in, the .sh scripts aren't executable by default. So when bootstrap.sh in my initial folder creates the new gitops-0-bootstrap folder and then tries to run the set-git-source.sh file that is inside of it, it fails because the newly created file is not executable.
I was wondering if anyone has run into a similar problem, and while I can shim in a fix in the set_git_source function, I am trying to use this repo as an imported submodule and not make any changes.
[logs.pdf](https://github.com/cloud-native-toolkit/multi-tenancy-gitops/files/7988733/logs.pdf)
Guide de contribution
Aucun guide de contribution indexé pour ce dépôt
Piste de recherche
Commencez par bootstrap.sh et sa fonction set_git_source, puis examinez scripts/set-git-source.sh dans le dossier gitops-0-bootstrap nouvellement créé. Reproduisez le flux de bootstrap dans le conteneur registry.access.redhat.com/ubi8/python-39 et vérifiez que set_git_source se termine sans erreur de permission refusée.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- docker, shell
- Domaine
- devops
- Type d'issue
- Bug
- Difficulté
- 2/5
- Temps estimé
- 1-3 heures
- Activité
- À l'abandon
- Clarté
- Clairement spécifiée
- Accessibilité débutants
- 35/100