when I run "docker-compose up -d“, then
Starting storj ... error
ERROR: for storj Cannot start service storj: failed to initialize logging driver: database is locked
ERROR: for storj Cannot start service storj: failed to initialize logging driver: database is locked
ERROR: Encountered errors while bringing up the project.
Alexey
December 5, 2022, 6:51am
2
Please post your docker-compose.yaml
file
I use this config about 1 month. today docker crashed
version: "3.5"
services:
storj:
image: storjlabs/storagenode:latest
network_mode: "host"
container_name: storj
volumes:
- type: bind
source: /volume1/storj/app/identity
target: /app/identity
- type: bind
source: /volume1/storj/app/config
target: /app/config
environment:
- WALLET="*****"
- EMAIL="*****"
- ADDRESS="*****:28967"
- STORAGE="1TB"
- http_proxy=http://127.0.0.1:10801
- https_proxy=http://127.0.0.1:10801
Alexey
December 5, 2022, 8:52am
4
Then perhaps it’s related so some updates either for docker or your OS. I could only suggest to try to restart the docker service
sudo systemctl restart docker
or even reboot your server.
phoenix
December 5, 2022, 11:28am
5
It is Synology docker’s problem.
I delete the docker, then rebuild it to solve.
refer:
So purchased a Synology DS1520+ to replace my 10 yr old ReadyNAS. Let me tell you I’ve been extremely disappointed with the OS proprietary packaging and utilities. This problem being one of many with the fact they decided logs should go into a database and not flat files…
Anyways, after running my container for about 2 weeks, it suddenly exited and would not restart. The one message I found said:
Start container storjlabs-storagenode1 failed: {“message”:“failed to initialize logging dri…
Problem: When you try to start a specific Docker container using the Synology NAS GUI, the container is being stopped unexpectedly and you see an error message like this in the logs: Start container mycontainer failed: {"message":"failed to...
Est. reading time: 2 minutes
1 Like