Symlink permission error when trying to use binarySource=install #368

Activity

1. florianklumb

   changed the title [-]Permission error when trying to use binarySource=install[/-] [+]Symlink permission error when trying to use binarySource=install[/+] on Apr 28, 2022
2. florianklumb

   closed this as completedon Apr 28, 2022
3. Chumper commented on Apr 28, 2022

   

   Chumper

   on Apr 28, 2022

   Contributor

   More actions

   How do you start the docker container?
4. florianklumb commented on Apr 28, 2022

   

   florianklumb

   on Apr 28, 2022

   Last edited by florianklumb

   Author

   More actions

   Here is an excerpt from the Jenkinsfile:

   pipeline {
       agent {
           docker {
               label buildAgents.DOCKER_AVAILABLE
               image 'renovate/renovate:32.32.5'
               args '-v /var/run/docker.sock:/var/run/docker.sock -v /tmp:/tmp'
           }
       }
   
       environment {
           CONFIGURATION = 'Release'
           TZ = 'Europe/Berlin'
           ENV = '/usr/local/etc/env'
           RENOVATE_TOKEN = credentials('...')
           RENOVATE_DOCKER_USER = 'root'
           GITHUB_COM_TOKEN = credentials('...')
           RENOVATE_BINARY_SOURCE = 'install'
           BUILDPACK = true
       }
   
       parameters {
           string defaultValue: '', description: '', name: 'RENOVATE_ARGS', trim: true
       }
   
       stages {
           stage('init') {
               steps {
                   sh 'renovate --version'
                   sh 'rm -f renovate.log'
               }
           }
   
           stage('renovate') {
               steps {
                   sh 'renovate --log-file renovate.log --log-file-level debug ${params.RENOVATE_ARGS}'
               }
           }
       }
   }
   
5. viceice commented on Apr 28, 2022

   

   viceice

   on Apr 28, 2022

   Member

   More actions

   @florianklumb why did you closed the issue?
6. florianklumb commented on Apr 28, 2022

   

   florianklumb

   on Apr 28, 2022

   Author

   More actions

   Sorry for the mixup. I thought I should've opened a discussion instead but you guys were too fast to reply :-)
7. containerbase

   locked and limited conversation to collaborators on Apr 28, 2022
8. viceice

   converted this issue into a discussion #370 on Apr 28, 2022