airhead
August 13, 2019, 6:36pm
1
Testing out the waters with silverblue and podman and hit this issue running rootless. I can seeminly run many other database systems via podman (mysql, mssql etc.) without issue but mongo will not run. I am running silverblue on hyperv on windows. Was able to boot a current version of ubuntu, install podman and run mongo with the same command so seems to be an issue with silverblue (or maybe fedora in general).
Also tried --privileged and same issue but sudo can start it up.
podman info
refi64
August 14, 2019, 3:17am
2
Have you tried comparing the versions between Ubuntu and Silverblue? Given that it works with sudo, I’d guess this might be an issue with rootless podman.
airhead
August 14, 2019, 6:25pm
3
Yes, there was a version difference and 1.5 not in the fedora repos yet but I built from source and same issue. Did also have the same issue on fedora workstation vm so not a silverblue issue but fedora in general. Seems rootless podman on ubuntu does use native overlayfs while others like fedora can only use fuse so may be related, going to open a issue on podman github I guess.
airhead
August 14, 2019, 9:11pm
4
In case anyone else has this or something similar. Found out it is a regression with fuse-overlayfs 0.5. Fixed in 0.5.1.
opened 06:32PM - 14 Aug 19 UTC
closed 09:10PM - 14 Aug 19 UTC
kind/bug
<!--
---------------------------------------------------
BUG REPORT INFORMATIO… N
---------------------------------------------------
Use the commands below to provide key information from your environment:
You do NOT have to include this information if this is a FEATURE REQUEST
**NOTE** A large number of issues reported against Podman are often found to already be fixed
in more current versions of the project. Before reporting an issue, please verify the
version you are running with `podman version` and compare it to the latest release
documented on the top of Podman's [README.md](../README.md). If they differ, please
update your version of Podman to the latest possible and retry your command before creating
an issue.
If you are filing a bug against `podman build`, please instead file a bug
against Buildah (https://github.com/containers/buildah/issues). Podman build
executes Buildah to perform container builds, and as such the Buildah
maintainers are best equipped to handle these bugs.
-->
**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
1. podman run --rm mongo:4
**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.
```
Version: 1.4.4
RemoteAPI Version: 1
Go Version: go1.12.7
OS/Arch: linux/amd64
```
**Output of `podman info --debug`:**
```
debug:
compiler: gc
git commit: ""
go version: go1.12.7
podman version: 1.4.4
host:
BuildahVersion: 1.9.0
Conmon:
package: podman-1.4.4-4.fc30.x86_64
path: /usr/libexec/podman/conmon
version: 'conmon version 1.0.0-dev, commit: 164df8af4e62dc759c312eab4b97ea9fb6b5f1fc'
Distribution:
distribution: fedora
version: "30"
MemFree: 547430400
MemTotal: 8260423680
OCIRuntime:
package: runc-1.0.0-93.dev.gitb9b6cc6.fc30.x86_64
path: /usr/bin/runc
version: |-
runc version 1.0.0-rc8+dev
commit: e3b4c1108f7d1bf0d09ab612ea09927d9b59b4e3
spec: 1.0.1-dev
SwapFree: 8396992512
SwapTotal: 8396992512
arch: amd64
cpus: 1
hostname: lordhelmet.hra.local
kernel: 5.2.7-200.fc30.x86_64
os: linux
rootless: true
uptime: 29m 22.41s
registries:
blocked: null
insecure: null
search:
- docker.io
- registry.fedoraproject.org
- quay.io
- registry.access.redhat.com
- registry.centos.org
store:
ConfigFile: /home/airhead/.config/containers/storage.conf
ContainerStore:
number: 1
GraphDriverName: overlay
GraphOptions:
- overlay.mount_program=/usr/bin/fuse-overlayfs
GraphRoot: /var/home/airhead/.local/share/containers/storage
GraphStatus:
Backing Filesystem: extfs
Native Overlay Diff: "false"
Supports d_type: "true"
Using metacopy: "false"
ImageStore:
number: 2
RunRoot: /tmp/1000
VolumePath: /var/home/airhead/.local/share/containers/storage/volumes
```
**Additional environment details (AWS, VirtualBox, physical, etc.):**
Using HyperV for all of these tests
2 Likes
