distribution: Registry 2.6.2 with s3 backend panic: runtime error: invalid memory address or nil pointer dereference
Hi! I’m using image registry:2.6.2 in k8s with s3-compatible service https://mcs.mail.ru/storage/ as backend.
After pushing couple layers I’ve got:
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x4a85a2]
goroutine 110 [running]:
panic(0xb97080, 0xc420012050)
/usr/local/go/src/runtime/panic.go:500 +0x1a1
github.com/docker/distribution/registry/storage/driver/s3-aws.(*driver).copy.func1(0xc42006dda0, 0x1, 0xc420323980, 0x1066a80, 0xc4206d1640, 0xc42044acc0, 0x5f, 0xc4203d7650, 0x69, 0xc4202219a0, ...)
/go/src/github.com/docker/distribution/registry/storage/driver/s3-aws/s3.go:742 +0x592
created by github.com/docker/distribution/registry/storage/driver/s3-aws.(*driver).copy
/go/src/github.com/docker/distribution/registry/storage/driver/s3-aws/s3.go:748 +0x6aa
Retest with registry:2.5.2: works fine, no any crush.
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Reactions: 7
- Comments: 23 (2 by maintainers)
Had the same issue (using the helm package) with registry:v2.7.1
For now I’ve forced the 2.5.2 image which seems to work:
Any news on when / which version this will be fixed? Latest tag today is still 2.7.1 (3 months old)
I’m also running into issues with registry panic’ing when talking to s3, and it works in master. What’s keeping from cutting a new release?
I switched over to https://gitlab.com/gitlab-org/container-registry/
2.7.1 is more like 9 months old. Very sad that there is so little movement in the various issues
Can you please spin a new release with the updated S3 SDK ?
Had this problem when using DigitalOcean Spaces, which appears to be Ceph under the covers. 2.5.2 works, though.
Encountered this issue recently with Ceph’s RADOSGW S3 storage. 2.6.2 works just fine, but 2.7 encounters the panic.
[edit]
To expand, this is using Ceph 12.2.12 without the use of the civetvweb frontend.
@oanogin 2.5.2 works fine
@ederst GitLab PM for the registry here. Actually, after surveying GitLab users, we’ve decided not to deprecate the proxy feature. Hopefully, that helps you stick with the GitLab Container Registry. Ping me if you have any issues.
I use
registry:2.7.1with DO Spaces S3 backend. I see the same error when requestingGET /v2/_catalog. Otherwise everything seems to be working fine. UPD./bin/registry garbage-collect /etc/docker/registry/config.ymlfails tooThe Ceph issue @r0ss3 references is supposedly fixed in Ceph 13.2.5 but I am still seeing this issue with that version of Ceph.
Same stroy as with @pilosus Using 2.7.1 with DO S3 getting error on /v2/_catalog
Downgrading to
registry:2.5.2solved the issue!@pilosus , you should try.
P.S. Stacktrace: