Issue using docker installation method on fedora 40 #870
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
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
The text was updated successfully, but these errors were encountered: