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

Issue using docker installation method on fedora 40 #870

Open
Ameenasuhani opened this issue May 13, 2024 · 2 comments
Open

Issue using docker installation method on fedora 40 #870

Ameenasuhani opened this issue May 13, 2024 · 2 comments
Labels
area/containers kind/bug Something isn't working priority/1 Should be fixed for next release severity/major Major loss of function, as specified in the requirements for this release, or existing in the curren

Comments

@Ameenasuhani
Copy link
Contributor

Describe the bug A clear and concise description of what the bug is.
Issue using docker installation method on fedora 40.

To Reproduce Steps to reproduce the behavior:
s3gw# docker run --name=s3gw -it -p 7480:7480 -e RGW_DEFAULT_USER_ACCESS_KEY="test" -e RGW_DEFAULT_USER_SECRET_KEY="test" -v data:/data quay.io/s3gw/s3gw:latest
did not load config file, using default settings.
2024-05-13T06:51:23.623+0000 7f1729a50f80 -1 Errors while parsing config file!
2024-05-13T06:51:23.623+0000 7f1729a50f80 -1 can't open ceph.conf: (2) No such file or directory
2024-05-13T06:51:23.650+0000 7f1729a50f80 -1 Errors while parsing config file!
2024-05-13T06:51:23.650+0000 7f1729a50f80 -1 can't open ceph.conf: (2) No such file or directory
2024-05-13T06:51:23.651+0000 7f1729a50f80 0 ceph version Development (no_version) reef (stable), process radosgw, pid 7
2024-05-13T06:51:23.651+0000 7f1729a50f80 0 framework: beast
2024-05-13T06:51:23.651+0000 7f1729a50f80 0 framework conf key: port, val: 7480
2024-05-13T06:51:23.663+0000 7f1729a50f80 0 rgw main: ERROR: hard open file limit is 1024 but we may need 2112 or more
2024-05-13T06:51:23.663+0000 7f1729a50f80 -1 Couldn't init storage provider (RADOS)
/s3gw/bin/entrypoint.sh: line 57: kill: (7) - No such process

Expected behavior A clear and concise description of what you expected to
happen.
s3gw container should be up and running

Desktop (please complete the following information):

OS: Fedora 40

Docker Version:
Version: 24.0.5
API version: 1.43

Additional context Add any other context about the problem here.

Workarounds:
Modified /etc/security/limits.conf to
username soft nofile 3000
username hard nofile 3000

Also tried setting
#ulimit -n 3000

Note: This issue is not seen with podman

@github-project-automation github-project-automation bot moved this to Backlog in S3GW May 13, 2024
@github-actions github-actions bot added the triage/waiting Waiting for triage label May 13, 2024
@jecluis jecluis added kind/bug Something isn't working priority/1 Should be fixed for next release area/containers severity/major Major loss of function, as specified in the requirements for this release, or existing in the curren and removed triage/waiting Waiting for triage labels May 13, 2024
@jecluis jecluis added this to s3gw May 13, 2024
@jecluis
Copy link
Contributor

jecluis commented May 13, 2024

@Ameenasuhani does the workaround work? This seems a fedora thing, and a lot less an s3gw thing. This might be a matter of documenting this as a requirement.

@Ameenasuhani
Copy link
Contributor Author

Ameenasuhani commented May 14, 2024

yes it worked for me using below command

$ docker run --ulimit nofile=4096:4096 -p 7480:7480 quay.io/s3gw/s3gw:latest

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/containers kind/bug Something isn't working priority/1 Should be fixed for next release severity/major Major loss of function, as specified in the requirements for this release, or existing in the curren
Projects
Status: No status
Development

No branches or pull requests

2 participants