Skip to content
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

Add NeoFS S3 Gateway image #40

Draft
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

cthulhu-rider
Copy link
Contributor

No description provided.

@cthulhu-rider cthulhu-rider added the enhancement Improving existing functionality label Nov 9, 2022
@cthulhu-rider cthulhu-rider self-assigned this Nov 9, 2022
aprasolova
aprasolova previously approved these changes Nov 9, 2022
@@ -1,4 +1,5 @@
NEOGO_VERSION=0.99.3
AIO_VERSION=0.32.0
AIO_VERSION=0.34.0
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we wait for #39?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Forgot to mark as draft.

@aprasolova
Copy link

On start, S3 ate fails with error

2022-11-09T12:38:15.798Z	info	s3-gw/app.go:235	using credentials	{"NeoFS": "0272e3f36426765720ec9b68ca10e32753ac4458ed9b17576f3af0564c31580756"}
2022-11-09T12:38:15.798Z	info	s3-gw/app_settings.go:159	added connection peer	{"address": "localhost:8080", "weight": 1}
2022-11-09T12:38:15.798Z	warn	s3-gw/app_settings.go:147	skip, empty address
2022-11-09T12:38:15.808Z	fatal	s3-gw/app.go:182	failed to create resolver	{"error": "unknown resolver: \"nns"}
main.(*App).initResolver

@cthulhu-rider cthulhu-rider marked this pull request as draft November 9, 2022 13:44
@cthulhu-rider
Copy link
Contributor Author

cthulhu-rider commented Nov 9, 2022

@KirillovDenis what's the reason of this error?

@aprasolova hmm I didn't encounter this error. Can you pls try with commenting S3_GW_RESOLVE_ORDER in s3/s3.env?

UPD: there was a mistake in s3/s3.env with redundant quote. Fixed @aprasolova

s3/s3.env Outdated

S3_GW_RESOLVE_ORDER=nns dns

S3_GW_DEFAULT_POLICY="REP 1"

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Here "REP 1" should be without quotes REP 1. Otherwise, S3 gate writes the error
fatal s3-gw/app.go:612 couldn't parse container default policy {"error": "policy: syntax error: line 1:0 mismatched input '\"REP 1\"' expecting 'REP'"}

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I still see REP 1 without quotes

Signed-off-by: Leonard Lyubich <[email protected]>
Use `sidechain` volume to store sidechain data and make it accessible
after restarts.

Signed-off-by: Leonard Lyubich <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Improving existing functionality
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants