tailscale-dev / tailscale-dev/tclip
Leverage skopeo for pipeline
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 265
- Forks
- 25
- PR merge metrics
- No merged PRs in 30d
Description
Currently the CI/CD process builds the container image, then loads it into Docker and uses Docker to push it. I've had fairly good luck with using https://github.com/containers/skopeo to push the Nix-built container image directly. It's a minor "optimization" (if you could call it that) but might be worth looking at.
Here's a rough example of where I'm using it for a personal repository: https://git.gmem.ca/arch/dref/src/branch/trunk/.gitea/workflows/test-build.yml#L36-L72
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Locate the repository's CI/CD workflow that builds and pushes the container image, then compare its Docker load and push steps with the linked test-build.yml example. Done means the pipeline pushes the Nix-built image directly through skopeo and completes successfully without loading it into Docker.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100