Hej, I use for this secret variables and store the access tokens or ssh keys in in one of this. A script running inside of the docker container uses sed magic for replacing string, when ever the direct usage of the secret variables is not possible. The ssh key is then written in a first step with something like
echo "$SECRET_PRIVATE_SSH" > ~/.ssh/id_ecdsa && chmod 600 ~/.ssh/id_ecdsa gitlab will not print the secret variables in clear format. https://docs.gitlab.com/ee/ci/variables/#via-the-ui Whenever possible you should use a deploy token, best would be to add this as well as the above mentioned ui variables. With the protected feature you can even prevent non privileged developers from stealing this secrets. https://docs.gitlab.com/ee/user/project/deploy_tokens/#creating-a-deploy-token Am 17.06.19 um 20:00 schrieb Rudolf Streif: > That's more of a Gitlab than Yocto question. I am doing this all the > time with my GL server on AWS. You need to add deploy a key to the > repo you want to access and then push the key to your Docker instance > from gitlab-ci.yaml from the repo that you are using with GL CI. > > :rjs > > On Mon, Jun 17, 2019, 07:20 Gabriele Zampieri <gabbla.mal...@gmail.com > <mailto:gabbla.mal...@gmail.com>> wrote: > > Hi all, > > does anyone have a guide on how to setup Yocto to run inside > docker? Right now I managed to trigger the build from GitLab, but > I'm facing an issue related to ssh keys (some recipes from my meta > layer are hosted on a privare repository). Probably this is not > the best mailing list to ask this kind of question, but it may > worth a try. > > Thank you, > Gabriele > -- > _______________________________________________ > yocto mailing list > yocto@yoctoproject.org <mailto:yocto@yoctoproject.org> > https://lists.yoctoproject.org/listinfo/yocto > >
-- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
