-
Notifications
You must be signed in to change notification settings - Fork 26
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
goroutine fatal when pushing big amount of images #154
Comments
workarounded with: |
OK, I got it, this looks to be an issue with improper goroutine isolation. ... or maybe ... default concurrency limits being too high (still we should not have such bogus error messages) |
Hey @glensc could you please share this One thing also I want to investigate - we have no deduplication of passed Docker repos, |
no, i can't share it for obvious reasons :) it has unique 415 images, all specified with tag (no regexps) from same gitlab docker registry using https. what other characteristics you need to know? the config was generated with gitlab-registry-usage |
OK! Well, the interesting part is: Are there any duplicates among image specifications? |
no duplicates. btw, shared my scripts: sciapp/gitlab-registry-usage#3 |
Great. Thank you! Meanwhile I will continue to develop "improper goroutine isolation" fix. |
here's one more, even with concurrency 1! |
this is supposed to fix it #158 (but I need a review from someone before merge) |
merged! https://github.com/ivanilves/lstags/releases/tag/v1.0.66 - let's promote it to stable if @glensc confirms concurrency issue is solved |
not solved. will post complete log in few hours
btw, does that commandline also pull images from source repo?
|
Yes! But it went from Please see the proposed fix in #160
Yes it does! 😉 Maybe we need to highlight this in README? 😇 P.S.: |
@glensc we released https://github.com/ivanilves/lstags/releases/tag/v1.0.67 could you please try it? 🙏 @ivanilves our current CI build runs low intensity tests, which is not optimal for detection of concurrency-related errors. We need to add a stress test to our CI build, so we will detect these errors before users do. WDYT? |
Anyway: #162 |
downloaded 1.0.67, either it works or still goroutine errors. can't say :) |
OK, so it probably works, but you need to run it more times to get representative statistics? 🙂 |
seems working now. i'll create new issue if problem occurs. |
in similar context as #153, but different scenario, got goroutine fatal errors when pushing ~400 images to registry.
the
registry:5000
is insecure registry confured via env:INSECURE_REGISTRY_EX=registry:5000
worked fine with 1 image with same configuration.
More complete output:
push_b_1a.log
The text was updated successfully, but these errors were encountered: