Cannot run rootless mongodb on fedora #3816
Labels
kind/bug
Categorizes issue or PR as related to a bug.
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
Comments
openshift-ci-robot
added
the
kind/bug
|
That looks like an ENXIO on chown of a unix socket? Can you try again with Otherwise, my suspicion might be an attempt to use a UID/GID that aren't available in the container. I can see a @giuseppe Might want to take a look here, too |
|
Hmmm. Would a |
|
Here is the output with debug: |
|
I think it is caused by a regression in fuse-overlayfs. Can you confirm you are using fuse-overlayfs 0.5? If that is the case, https://bodhi.fedoraproject.org/updates/FEDORA-2019-33bf337c28 might solve the issue you are seeing |
|
Yes I am running fuse-overlayfs 0.5. Upgraded to 0.5.1-2 from the testing repository and the issue was resolved, hopefully they push that package to stable soon. Thanks |
|
@aaronhagopian it needs karma to get released -> https://bodhi.fedoraproject.org/updates/FEDORA-2019-33bf337c28 I'd encourage you to give it karma |
@baude Done, thanks for the heads up. |
|
Can we get one more good karma it will come out. |
github-actions
bot
added
the
locked - please file new issue/PR
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
Running mongodb rootless on fedora systems errors out while running on Ubuntu seems fine.
Steps to reproduce the issue:
Running on Fedora 30
Describe the results you received:
$ podman run --rm mongo:4
chown: changing ownership of '/proc/1/fd/1': Permission denied
chown: changing ownership of '/proc/1/fd/2': Permission denied
2019-08-14T18:28:58.570+0000 I CONTROL [main] Automatically disabling TLS 1.0, to force-enable TLS 1.0 specify --sslDisabledProtocols 'none'
2019-08-14T18:28:58.575+0000 I CONTROL [initandlisten] MongoDB starting : pid=1 port=27017 dbpath=/data/db 64-bit host=69401cbc276b
2019-08-14T18:28:58.576+0000 I CONTROL [initandlisten] db version v4.2.0
2019-08-14T18:28:58.576+0000 I CONTROL [initandlisten] git version: a4b751dcf51dd249c5865812b390cfd1c0129c30
2019-08-14T18:28:58.576+0000 I CONTROL [initandlisten] OpenSSL version: OpenSSL 1.1.1 11 Sep 2018
2019-08-14T18:28:58.576+0000 I CONTROL [initandlisten] allocator: tcmalloc
2019-08-14T18:28:58.576+0000 I CONTROL [initandlisten] modules: none
2019-08-14T18:28:58.577+0000 I CONTROL [initandlisten] build environment:
2019-08-14T18:28:58.577+0000 I CONTROL [initandlisten] distmod: ubuntu1804
2019-08-14T18:28:58.577+0000 I CONTROL [initandlisten] distarch: x86_64
2019-08-14T18:28:58.577+0000 I CONTROL [initandlisten] target_arch: x86_64
2019-08-14T18:28:58.577+0000 I CONTROL [initandlisten] options: { net: { bindIp: "*" } }
2019-08-14T18:28:58.578+0000 E NETWORK [initandlisten] Failed to chmod socket file /tmp/mongodb-27017.sock No such device or address
2019-08-14T18:28:58.578+0000 F - [initandlisten] Fatal Assertion 40487 at src/mongo/transport/transport_layer_asio.cpp 725
2019-08-14T18:28:58.578+0000 F - [initandlisten]
***aborting after fassert() failure
Describe the results you expected:
Additional information you deem important (e.g. issue happens only occasionally):
Output of
podman version:Problem on fedora 30, built from source to try 1.5.0 since that worked fine on Ubuntu but had same issue w/ 1.5.0 from source.
Output of
podman info --debug:Additional environment details (AWS, VirtualBox, physical, etc.):
Using HyperV for all of these tests
The text was updated successfully, but these errors were encountered: