-
Notifications
You must be signed in to change notification settings - Fork 3
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
Slim option doesn't work in CircleCI #26
Comments
I just noticed that the "large" renovate image uses node 14 with npm 6 and I need npm 7. I will try to look into this and make it work for node at least. I'll keep you posted about my findings! |
Ok next issue was with access rights to folders, passing Following one: not recognizing that the package-lock was changed, renovate is relying on volumes to work but that doesn't work on CircleCI:
Source: https://circleci.com/docs/2.0/building-docker-images/#mounting-folders |
After thinking about the problem I described above I would just disable the slim option for the circle ci orb. It's clearly not made for it. To solve my personal problem I'm planning on using |
Thanks for the findings! Good point, I'll remove the |
Orb version:
3.0.0
What happened:
When turning on the slim option renovate does not work. When using the slim container the binarySource option is set to docker in the dockerfile. Using this option means that new child docker container/processes will be spawned. To use this in CircleCI you have to add the setup_remote_docker step.
Just FYI when using adding that step locally I stil had some access issue but didn't have the time to look into it.
Expected behavior:
When using the slim option the orb takes all measures so this can run smoothly.
The text was updated successfully, but these errors were encountered: