Make registry tests using docker.socket dockerless
Open
Nobody has claimed this yet.
area/tests
component/build
component/image
component/imageregistry
lifecycle/frozen
priority/P1
sig/developer-experience
- Dominant language
- Go
- Stars
- 8.7k
- Forks
- 4.8k
- Avg merge
- 4d 10h
- Merged PRs (30d)
- 53
Description
The tests using the docker socket fail because the access is not granted anymore in pods.
Therefore they are now being marked with [local].
This issue is a reminder to rewrite the tests in a dockerless way.
See the related discussion:
And related [local] PRs:
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.
Assessment
This issue has not been assessed yet.