You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that PR #6194 has been inactive for a few months. If the original author is no longer working on this, I would love to take over the issue and give it a try.
I am a college student studying computer science and new to open-source contributions. I am also currently learning the Go language. Would it be okay for someone like me to take over this issue?
If you give me permission, I will do my best to learn and contribute! I have great respect for you all and aspire to be a great engineer like you.
(P.S. Since English is not my first language, I used a translation tool and AI. Please bear with me if the sentences sound a bit awkward!)
Regression coverage for private registry auth is already implemented in #6940 (addresses #5963). Happy to help review or rebase that PR if maintainers want it moved forward.
The CI failures look caused by a bad htpasswd volume path in e2e/compose-env.yaml (paths are resolved relative to the compose file, so ./e2e/testdata/... never mounted). I'm reopening #7007 with that fix plus a small compose cleanup (privateregistry service name, depends_on).
Hey, just following up on the PR I raised. I noticed that no reviewer has been assigned yet, and I wanted to check in to make sure it doesn't go stale. Would someone be able to take a look when they get a chance? Thanks!
Activity
RASHMIBB23 commentedon Apr 10, 2025
Antraxmin commentedon Apr 29, 2025
Can I start working on it?
AryanSharma9917 commentedon Jul 17, 2025
Hey @Benehiko,
I'm interested in working on this issue. Is it still available for contributions? Let me know if I can get assigned to it!
Thanks!
vvoland commentedon Jul 17, 2025
Yes, feel free to open a PR
dev-seonghyeon commentedon Apr 15, 2026
Hello @vvoland and @AryanSharma9917,
I noticed that PR #6194 has been inactive for a few months. If the original author is no longer working on this, I would love to take over the issue and give it a try.
I am a college student studying computer science and new to open-source contributions. I am also currently learning the Go language. Would it be okay for someone like me to take over this issue?
If you give me permission, I will do my best to learn and contribute! I have great respect for you all and aspire to be a great engineer like you.
(P.S. Since English is not my first language, I used a translation tool and AI. Please bear with me if the sentences sound a bit awkward!)
lohitkolluri commentedon May 26, 2026
Regression coverage for private registry auth is already implemented in #6940 (addresses #5963). Happy to help review or rebase that PR if maintainers want it moved forward.
vvoland commentedon May 26, 2026
#6940 looks stale. Feel free to carry it forward!
lohitkolluri commentedon May 26, 2026
Thanks @vvoland — I'll carry #6940 forward via #7007.
The CI failures look caused by a bad htpasswd volume path in
e2e/compose-env.yaml(paths are resolved relative to the compose file, so./e2e/testdata/...never mounted). I'm reopening #7007 with that fix plus a small compose cleanup (privateregistryservice name,depends_on).e2e: add private registry pull/push regression test
e2e: add private registry pull/push regression test
e2e: add private registry pull/push regression test
e2e: add private registry pull/push regression test
e2e: add private registry pull/push regression test
e2e: add private registry pull/push regression test
e2e: add private registry pull/push regression test
e2e: add private registry pull/push regression test
e2e: add private registry pull/push regression test
lohitkolluri commentedon Jun 9, 2026
Hey, just following up on the PR I raised. I noticed that no reviewer has been assigned yet, and I wanted to check in to make sure it doesn't go stale. Would someone be able to take a look when they get a chance? Thanks!