Bring back Kaniko for building images
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- docker, groovy
- Domain
- build-system, devops, infrastructure
Research direction
Start by locating the Jenkins image-building configuration in this repository, then compare it with the old main agent image-building repository linked in the issue. Determine how the current Docker-in-Docker setup is wired and what Kaniko configuration must be restored. Done means image builds run successfully through a Kaniko build agent without Docker-in-Docker.
Written by the indexing model from the issue text.
Description
When moving Jenkins I used the latest agents I had been working on coincidentally which were docker-in-docker based which isn't great for security. In the past we avoided that by using a Kaniko build agent to make the images. There's really no reason other than a bit of time to not just go back to that but time has this annoying thing about being finite and I'm trying to move on to some other priority stuff for the moment. To here a reminder goes!
Old main agent image building repo as of this writing: https://github.com/MovingBlocks/JenkinsAgentPrecachedJava
- Dominant language
- Groovy
- Stars
- 0
- Forks
- 2
- Avg merge
- 13m
- Merged PRs (30d)
- 7
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 MovingBlocks/Logistics
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
MovingBlocks/Logistics#5 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
All issues in MovingBlocks/Logistics
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
bjverde/adianti-fork-template#103 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
gfx-rs/wgpu-native#636 ·
-
dependencies priority high
Difficulty 1/5 Under an hour Newbie friendliness 88/100
martin-francois/symphony-trello#865 ·
Maintainers usually reply within 1 day
-
area:protocol bug
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
dependabot-security-finding needs-triage priority/p0
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
cdk8s-team/cdk8s-examples#981 ·
Maintainers usually reply within 1 day