-
Notifications
You must be signed in to change notification settings - Fork 2
Known Issues
David Zager edited this page Feb 26, 2018
·
6 revisions
There is some discussion of drawbacks here
The pod fails with this in the log:
INFO ==> Starting mongodb...
sed: can't read /bitnami/mongodb/conf/mongodb.conf: No such file or directory
INFO ==> Starting mongod...
error: failed switching to "mongo": unable to find user mongo: no matching entries in passwd file
The problem with the mongodb image is that it does not support being run as a non-root user. See https://github.com/bitnami/bitnami-docker-mongodb/issues/75
The pod fails with this in the log:
initdb: could not look up effective user ID 1000280000: user does not exist
Found in the deployment resource details after observing that deployment was failing:
message: 'pods "ee3658f8-f55a-434c-a59a-af19f917c760-redis-5d84c85d96-" is forbidden:
unable to validate against any security context constraint: [fsGroup: Invalid
value: []int64{1001}: 1001 is not an allowed group spec.containers[0].securityContext.securityContext.runAsUser:
Invalid value: 1001: must be in the ranges: [1000110000, 1000119999]]'
reason: FailedCreate
status: "True"
type: ReplicaFailure
The mongodb
pod fails with this in the log:
INFO ==> Starting mongodb...
sed: can't read /bitnami/mongodb/conf/mongodb.conf: No such file or directory
INFO ==> Starting mongod...
error: failed switching to "mongo": unable to find user mongo: no matching entries in passwd file
See mongodb for details.
The rocketchat
pod initially runs fine, but then it fails likely because it can't connect to mongodb.