You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I get a warning regarding vm.max_map_count when launching a new MongoDB 6.0.15 container using podman.
Steps to reproduce the issue
Steps to reproduce the issue
podman run --name mongo --rm -p 27018:27017 -d mongo:6.0
mongosh --port 27018 --host localhost
(look at the latest warning under: "The server generated these startup warnings when booting")
Describe the results you received
The first 2 warnings are expected because I'm not using an XFS filesystem and didn't configure any security, but the third one shouldn't be there:
------
The server generated these startup warnings when booting
2024-05-31T00:19:51.658+00:00: Using the XFS filesystem is strongly recommended with the WiredTiger storage engine. See http://dochub.mongodb.org/core/prodnotes-filesystem
2024-05-31T00:19:51.933+00:00: Access control is not enabled for the database. Read and write access to data and configuration is unrestricted
2024-05-31T00:19:51.933+00:00: vm.max_map_count is too low
------
Describe the results you expected
No warning regarding vm.max_map_count as it's really high by default on Ubuntu 24.04 (1048576).
podman info output
host:
arch: amd64buildahVersion: 1.33.5cgroupControllers:
- cpu
- memory
- pidscgroupManager: systemdcgroupVersion: v2conmon:
package: conmon_2.1.10+ds1-1build2_amd64path: /usr/bin/conmonversion: 'conmon version 2.1.10, commit: unknown'cpuUtilization:
idlePercent: 99.55systemPercent: 0.2userPercent: 0.25cpus: 4databaseBackend: sqlitedistribution:
codename: nobledistribution: ubuntuversion: "24.04"eventLogger: journaldfreeLocks: 2045hostname: my-vmidMappings:
gidmap:
- container_id: 0host_id: 1000size: 1
- container_id: 1host_id: 100000size: 65536uidmap:
- container_id: 0host_id: 1000size: 1
- container_id: 1host_id: 100000size: 65536kernel: 6.8.0-31-genericlinkmode: dynamiclogDriver: journaldmemFree: 2595860480memTotal: 4105641984networkBackend: netavarknetworkBackendInfo:
backend: netavarkdns:
package: aardvark-dns_1.4.0-5_amd64path: /usr/lib/podman/aardvark-dnsversion: aardvark-dns 1.4.0package: netavark_1.4.0-4_amd64path: /usr/lib/podman/netavarkversion: netavark 1.4.0ociRuntime:
name: crunpackage: crun_1.14.1-1_amd64path: /usr/bin/crunversion: |- crun version 1.14.1 commit: de537a7965bfbe9992e2cfae0baeb56a08128171 rundir: /run/user/1000/crun spec: 1.0.0 +SYSTEMD +SELINUX +APPARMOR +CAP +SECCOMP +EBPF +WASM:wasmedge +YAJLos: linuxpasta:
executable: /usr/bin/pastapackage: passt_0.0~git20240220.1e6f92b-1_amd64version: | pasta unknown version Copyright Red Hat GNU General Public License, version 2 or later <https://www.gnu.org/licenses/old-licenses/gpl-2.0.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law.remoteSocket:
exists: falsepath: /run/user/1000/podman/podman.socksecurity:
apparmorEnabled: falsecapabilities: CAP_CHOWN,CAP_DAC_OVERRIDE,CAP_FOWNER,CAP_FSETID,CAP_KILL,CAP_NET_BIND_SERVICE,CAP_SETFCAP,CAP_SETGID,CAP_SETPCAP,CAP_SETUID,CAP_SYS_CHROOTrootless: trueseccompEnabled: trueseccompProfilePath: /usr/share/containers/seccomp.jsonselinuxEnabled: falseserviceIsRemote: falseslirp4netns:
executable: /usr/bin/slirp4netnspackage: slirp4netns_1.2.1-1build2_amd64version: |- slirp4netns version 1.2.1 commit: 09e31e92fa3d2a1d3ca261adaeb012c8d75a8194 libslirp: 4.7.0 SLIRP_CONFIG_VERSION_MAX: 4 libseccomp: 2.5.5swapFree: 4105170944swapTotal: 4105170944uptime: 0h 39m 56.00svariant: ""plugins:
authorization: nulllog:
- k8s-file
- none
- passthrough
- journaldnetwork:
- bridge
- macvlan
- ipvlanvolume:
- localregistries: {}store:
configFile: /home/myuser/.config/containers/storage.confcontainerStore:
number: 1paused: 0running: 1stopped: 0graphDriverName: overlaygraphOptions: {}graphRoot: /home/myuser/.local/share/containers/storagegraphRootAllocated: 33632829440graphRootUsed: 8830066688graphStatus:
Backing Filesystem: extfsNative Overlay Diff: "true"Supports d_type: "true"Supports shifting: "false"Supports volatile: "true"Using metacopy: "false"imageCopyTmpDir: /var/tmpimageStore:
number: 1runRoot: /run/user/1000/containerstransientStore: falsevolumePath: /home/myuser/.local/share/containers/storage/volumesversion:
APIVersion: 4.9.3Built: 0BuiltTime: Thu Jan 1 00:00:00 1970GitCommit: ""GoVersion: go1.22.1Os: linuxOsArch: linux/amd64Version: 4.9.3
Podman in a container
No
Privileged Or Rootless
Rootless
Upstream Latest Release
No
Additional environment details
This was tested on a vanilla Ubuntu Server 24.04 LTS with the default value of max_map_count:
cat /proc/sys/vm/max_map_count
1048576
Additional information
Please note that I don't get this warning when running a standalone MongoDB instance on the same server:
Current Mongosh Log ID: 665918c756b78c6261a26a12
Connecting to: mongodb://localhost:27017/?directConnection=true&serverSelectionTimeoutMS=2000&appName=mongosh+2.2.6
Using MongoDB: 6.0.15
Using Mongosh: 2.2.6
For mongosh info see: https://docs.mongodb.com/mongodb-shell/
------
The server generated these startup warnings when booting
2024-05-30T23:51:41.974+00:00: Using the XFS filesystem is strongly recommended with the WiredTiger storage engine. See http://dochub.mongodb.org/core/prodnotes-filesystem
2024-05-30T23:51:42.270+00:00: Access control is not enabled for the database. Read and write access to data and configuration is unrestricted
------
The text was updated successfully, but these errors were encountered:
Issue Description
I get a warning regarding vm.max_map_count when launching a new MongoDB 6.0.15 container using podman.
Steps to reproduce the issue
Steps to reproduce the issue
Describe the results you received
The first 2 warnings are expected because I'm not using an XFS filesystem and didn't configure any security, but the third one shouldn't be there:
Describe the results you expected
No warning regarding vm.max_map_count as it's really high by default on Ubuntu 24.04 (1048576).
podman info output
Podman in a container
No
Privileged Or Rootless
Rootless
Upstream Latest Release
No
Additional environment details
This was tested on a vanilla Ubuntu Server 24.04 LTS with the default value of max_map_count:
Additional information
Please note that I don't get this warning when running a standalone MongoDB instance on the same server:
The text was updated successfully, but these errors were encountered: