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
{{ message }}
This repository has been archived by the owner on Dec 29, 2023. It is now read-only.
These containers should use readOnlyRootFilesystem: false.
I can provided a Pull Request if you agree with the solution.
#Carts DB and Orders DB log message:
DBException in initAndListen, terminating","attr":{"error":"DBPathInUse: Unable to create/open the lock file: /data/db/mongod.lock (Read-only file system). Ensure the user executing mongod is the owner of the lock file and has the appropriate permissions. Also make sure that another mongod instance is not already running on the /data/db directory"}}
RabbitMQ log message:
chown: changing ownership of '/var/lib/rabbitmq/.bash_logout': Read-only file system
chown: changing ownership of '/var/lib/rabbitmq/.bashrc': Read-only file system
chown: changing ownership of '/var/lib/rabbitmq/.profile': Read-only file system
chown: changing ownership of '/var/lib/rabbitmq/mnesia': Read-only file system
chown: changing ownership of '/var/lib/rabbitmq': Read-only file system
User DB log message:
chown: changing ownership of '/data/configdb': Read-only file system
chown: changing ownership of '/data/db': Read-only file system
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Problem
containers fail because their Root Filesystems are marked as readonly in the Kubernetes deployment file: https://github.com/microservices-demo/microservices-demo/blob/master/deploy/kubernetes/complete-demo.yaml
These containers should use readOnlyRootFilesystem: false.
I can provided a Pull Request if you agree with the solution.
#Carts DB and Orders DB log message:
DBException in initAndListen, terminating","attr":{"error":"DBPathInUse: Unable to create/open the lock file: /data/db/mongod.lock (Read-only file system). Ensure the user executing mongod is the owner of the lock file and has the appropriate permissions. Also make sure that another mongod instance is not already running on the /data/db directory"}}
RabbitMQ log message:
chown: changing ownership of '/var/lib/rabbitmq/.bash_logout': Read-only file system
chown: changing ownership of '/var/lib/rabbitmq/.bashrc': Read-only file system
chown: changing ownership of '/var/lib/rabbitmq/.profile': Read-only file system
chown: changing ownership of '/var/lib/rabbitmq/mnesia': Read-only file system
chown: changing ownership of '/var/lib/rabbitmq': Read-only file system
User DB log message:
chown: changing ownership of '/data/configdb': Read-only file system
chown: changing ownership of '/data/db': Read-only file system
The text was updated successfully, but these errors were encountered: