# Invalid configuration file key and moved db, orders and logs **URL:** \ **Category:** FAQ\ **Tags:** docker, linux\ **Created:** [March 22, 2024, 7:25am UTC](https://forum.storj.io/t/invalid-configuration-file-key-and-moved-db-orders-and-logs/25604 "2024-03-22T07:25:11Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![CubeFan](https://storj.bcdn.literatehosting.com/letter_avatar/cubefan/32/5_5575768a8748004e209b776fc1b2916d.png) [@CubeFan](https://forum.storj.io/u/CubeFan)\ **Post date:** [March 22, 2024, 7:25am UTC](https://forum.storj.io/t/invalid-configuration-file-key-and-moved-db-orders-and-logs/25604/1 "2024-03-22T07:25:11Z")
Hello everyone, I have a few comprehension questions. I would like to move the logs, orders and DB from my existing nodes to an SSD. To test this, I have created a test node. Unfortunately, I get “errors” in the container logs and I don’t understand why. > **Logs Docker Container** > > ```auto > 2024-03-21T21:56:33Z INFO Configuration loaded {"Process": "storagenode-updater", "Location": "/app/config/config.yaml"} > 2024-03-21T21:56:33Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "console.address"} > 2024-03-21T21:56:33Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "contact.external-address"} > 2024-03-21T21:56:33Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "server.private-address"} > 2024-03-21T21:56:33Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "storage.allocated-disk-space"} > 2024-03-21T21:56:33Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "storage.path"} > 2024-03-21T21:56:33Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "storage.allocated-bandwidth"} > 2024-03-21T21:56:33Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "operator.email"} > 2024-03-21T21:56:33Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "storage2.database-dir"} > 2024-03-21T21:56:33Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "healthcheck.enabled"} > 2024-03-21T21:56:33Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "server.address"} > 2024-03-21T21:56:33Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "storage2.orders.path"} > 2024-03-21T21:56:33Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "healthcheck.details"} > 2024-03-21T21:56:33Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "operator.wallet"} > 2024-03-21T21:56:33Z INFO Anonymized tracing enabled {"Process": "storagenode-updater"} > 2024-03-21T21:56:33Z INFO Running on version {"Process": "storagenode-updater", "Service": "storagenode-updater", "Version": "v1.95.1"} > 2024-03-21T21:56:33Z INFO Downloading versions. {"Process": "storagenode-updater", "Server Address": "https://version.storj.io"} > 2024-03-21T21:56:33Z INFO Current binary version {"Process": "storagenode-updater", "Service": "storagenode", "Version": "v1.95.1"} > 2024-03-21T21:56:33Z INFO New version is being rolled out but hasn't made it to this node yet {"Process": "storagenode-updater", "Service": "storagenode"} > 2024-03-21T21:56:33Z INFO Current binary version {"Process": "storagenode-updater", "Service": "storagenode-updater", "Version": "v1.95.1"} > 2024-03-21T21:56:33Z INFO New version is being rolled out but hasn't made it to this node yet {"Process": "storagenode-updater", "Service": "storagenode-updater"} > > ``` But when I look at the logs from the node, everything seems to work as intended. The 3 folders on the SSD are also being used. > **Node Logs** > > ```auto > 2024-03-22T06:38:54Z INFO Configuration loaded {"process": "storagenode", "Location": "/app/config/config.yaml"} > 2024-03-22T06:38:54Z INFO Anonymized tracing enabled {"process": "storagenode"} > 2024-03-22T06:38:54Z INFO Operator email {"process": "storagenode", "Address": "kroll.maik@hotmail.de"} > 2024-03-22T06:38:54Z INFO Operator wallet {"process": "storagenode", "Address": "0x90b8ff9674bcde6f428ba6184dd326b33f691775"} > 2024-03-22T06:38:54Z INFO server kernel support for server-side tcp fast open remains disabled. {"process": "storagenode"} > 2024-03-22T06:38:54Z INFO server enable with: sysctl -w net.ipv4.tcp_fastopen=3 {"process": "storagenode"} > 2024-03-22T06:38:54Z INFO Telemetry enabled {"process": "storagenode", "instance ID": "1wjKxs8agg7fXLSJCufxVCvEhxE16cC2621fJDF8f3rdp5H5LB"} > 2024-03-22T06:38:54Z INFO Event collection enabled {"process": "storagenode", "instance ID": "1wjKxs8agg7fXLSJCufxVCvEhxE16cC2621fJDF8f3rdp5H5LB"} > 2024-03-22T06:38:54Z INFO db.migration Database Version {"process": "storagenode", "version": 54} > 2024-03-22T06:38:54Z INFO preflight:localtime start checking local system clock with trusted satellites' system clock. {"process": "storagenode"} > 2024-03-22T06:38:55Z INFO preflight:localtime local system clock is in sync with trusted satellites' system clock. {"process": "storagenode"} > 2024-03-22T06:38:55Z INFO bandwidth Performing bandwidth usage rollups {"process": "storagenode"} > 2024-03-22T06:38:55Z INFO Node 1wjKxs8agg7fXLSJCufxVCvEhxE16cC2621fJDF8f3rdp5H5LB started {"process": "storagenode"} > 2024-03-22T06:38:55Z INFO Public server started on [::]:28967 {"process": "storagenode"} > 2024-03-22T06:38:55Z INFO Private server started on 127.0.0.1:7778 {"process": "storagenode"} > 2024-03-22T06:38:55Z INFO failed to sufficiently increase receive buffer size (was: 208 kiB, wanted: 2048 kiB, got: 416 kiB). See https://github.com/quic-go/quic-go/wiki/UDP-Buffer-Sizes for details. {"process": "storagenode"} > 2024-03-22T06:38:55Z INFO pieces:trash emptying trash started {"process": "storagenode", "Satellite ID": "12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs"} > 2024-03-22T06:38:55Z INFO pieces:trash emptying trash started {"process": "storagenode", "Satellite ID": "1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE"} > 2024-03-22T06:38:55Z INFO pieces:trash emptying trash started {"process": "storagenode", "Satellite ID": "121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6"} > 2024-03-22T06:38:55Z INFO trust Scheduling next refresh {"process": "storagenode", "after": "7h34m1.350462617s"} > 2024-03-22T06:38:55Z INFO pieces:trash emptying trash started {"process": "storagenode", "Satellite ID": "12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S"} > 2024-03-22T06:38:59Z INFO lazyfilewalker.used-space-filewalker starting subprocess {"process": "storagenode", "satelliteID": "12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs"} > 2024-03-22T06:38:59Z INFO lazyfilewalker.used-space-filewalker subprocess started {"process": "storagenode", "satelliteID": "12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs"} > 2024-03-22T06:38:59Z INFO lazyfilewalker.used-space-filewalker.subprocess Database started {"process": "storagenode", "satelliteID": "12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs", "process": "storagenode"} > 2024-03-22T06:38:59Z INFO lazyfilewalker.used-space-filewalker.subprocess used-space-filewalker started {"process": "storagenode", "satelliteID": "12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs", "process": "storagenode"} > 2024-03-22T06:38:59Z INFO lazyfilewalker.used-space-filewalker.subprocess used-space-filewalker completed {"process": "storagenode", "satelliteID": "12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs", "process": "storagenode", "piecesTotal": 4305664, "piecesContentSize": 4292352} > 2024-03-22T06:38:59Z INFO lazyfilewalker.used-space-filewalker subprocess finished successfully {"process": "storagenode", "satelliteID": "12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs"} > 2024-03-22T06:38:59Z INFO lazyfilewalker.used-space-filewalker starting subprocess {"process": "storagenode", "satelliteID": "12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S"} > 2024-03-22T06:38:59Z INFO lazyfilewalker.used-space-filewalker subprocess started {"process": "storagenode", "satelliteID": "12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S"} > 2024-03-22T06:38:59Z INFO lazyfilewalker.used-space-filewalker.subprocess Database started {"process": "storagenode", "satelliteID": "12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S", "process": "storagenode"} > 2024-03-22T06:38:59Z INFO lazyfilewalker.used-space-filewalker.subprocess used-space-filewalker started {"process": "storagenode", "satelliteID": "12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S", "process": "storagenode"} > 2024-03-22T06:38:59Z INFO lazyfilewalker.used-space-filewalker.subprocess used-space-filewalker completed {"process": "storagenode", "satelliteID": "12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S", "process": "storagenode", "piecesTotal": 4828416, "piecesContentSize": 4810496} > 2024-03-22T06:38:59Z INFO lazyfilewalker.used-space-filewalker subprocess finished successfully {"process": "storagenode", "satelliteID": "12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S"} > > ``` Do you have any idea what the problem could be? It seems to be the config.yaml but I don’t understand why. Here are my configs: > **Docker-compose.yml** > > ```auto > version: "3" > services: > storj-node: > image: storjlabs/storagenode:latest > container_name: "storj-node${NODE_ID}" > restart: unless-stopped > stop_grace_period: 300s > ports: > - "140${NODE_ID}:14002/tcp" > - "289${NODE_ID}:28967/tcp" > - "289${NODE_ID}:28967/udp" > volumes: > - "${NODE_DATA}:/app/config/storage" > - "${NODE_IDENTITY}:/app/identity" > - "${NODE_CONFIG}/config.yaml:/app/config/config.yaml" > - "${NODE_ORDERS}:/app/config/orders" > - "${NODE_DB}:/app/config/db" > - "${NODE_LOGS}:/app/config/logs" > environment: > - "EMAIL=${NODE_EMAIL}" > - "ADDRESS=${NODE_EXTERNAL}" > - "STORAGE=${NODE_STORAGE}" > - "WALLET=${NODE_WALLET}" > - "SETUP=false" > - "AUTO_UPDATE=true" > > ``` > **.env** > > ```auto > NODE_ID=99 > NODE_EMAIL=xxxxxxx > NODE_EXTERNAL=xxxxxxx:28999 > NODE_STORAGE=0.9TB > NODE_WALLET=xxxxxxx > NODE_IDENTITY=/mnt/storj_node_test/identity/ > NODE_DATA=/mnt/storj_node_test/storage/ > NODE_ORDERS=/mnt/storj_ssd/storj_node_test/orders/ > NODE_LOGS=/mnt/storj_ssd/storj_node_test/logs/ > NODE_DB=/mnt/storj_ssd/storj_node_test/db/ > NODE_CONFIG=/mnt/storj_node_test/ > > ``` > **config.yaml** > > ```auto > # how frequently bandwidth usage rollups are calculated > # bandwidth.interval: 1h0m0s > > # how frequently expired pieces are collected > # collector.interval: 1h0m0s > > # use color in user interface > # color: false > > # server address of the api gateway and frontend app > console.address: :14002 > > # path to static resources > # console.static-dir: "" > > # the public address of the node, useful for nodes behind NAT > contact.external-address: "" > > # how frequently the node contact chore should run > # contact.interval: 1h0m0s > > # Maximum Database Connection Lifetime, -1ns means the stdlib default > # db.conn_max_lifetime: 30m0s > > # Maximum Amount of Idle Database connections, -1 means the stdlib default > # db.max_idle_conns: 1 > > # Maximum Amount of Open Database connections, -1 means the stdlib default > # db.max_open_conns: 5 > > # address to listen on for debug endpoints > # debug.addr: 127.0.0.1:0 > > # expose control panel > # debug.control: false > > # If set, a path to write a process trace SVG to > # debug.trace-out: "" > > # open config in default editor > # edit-conf: false > > # in-memory buffer for uploads > # filestore.write-buffer-size: 128.0 KiB > > # how often to run the chore to check for satellites for the node to exit. > # graceful-exit.chore-interval: 1m0s > > # the minimum acceptable bytes that an exiting node can transfer per second to the new node > # graceful-exit.min-bytes-per-second: 5.00 KB > > # the minimum duration for downloading a piece from storage nodes before timing out > # graceful-exit.min-download-timeout: 2m0s > > # number of concurrent transfers per graceful exit worker > # graceful-exit.num-concurrent-transfers: 5 > > # number of workers to handle satellite exits > # graceful-exit.num-workers: 4 > > # Enable additional details about the satellite connections via the HTTP healthcheck. > healthcheck.details: false > > # Provide health endpoint (including suspension/audit failures) on main public port, but HTTP protocol. > healthcheck.enabled: true > > # path to the certificate chain for this identity > identity.cert-path: identity/identity.cert > > # path to the private key for this identity > identity.key-path: identity/identity.key > > # if true, log function filename and line number > # log.caller: false > > # if true, set logging to development mode > # log.development: false > > # configures log encoding. can either be 'console', 'json', 'pretty', or 'gcloudlogging'. > # log.encoding: "" > > # the minimum log level to log > log.level: info > > # can be stdout, stderr, or a filename > log.output: "/app/config/logs/node.log" > > # if true, log stack traces > # log.stack: false > > # address(es) to send telemetry to (comma-separated) > # metrics.addr: collectora.storj.io:9000 > > # application name for telemetry identification. Ignored for certain applications. > # metrics.app: storagenode > > # application suffix. Ignored for certain applications. > metrics.app-suffix: -alpha > > # address(es) to send telemetry to (comma-separated) > # metrics.event-addr: eventkitd.datasci.storj.io:9002 > > # instance id prefix > # metrics.instance-prefix: "" > > # how frequently to send up telemetry. Ignored for certain applications. > metrics.interval: 30m0s > > # maximum duration to wait before requesting data > # nodestats.max-sleep: 5m0s > > # how often to sync reputation > # nodestats.reputation-sync: 4h0m0s > > # how often to sync storage > # nodestats.storage-sync: 12h0m0s > > # operator email address > operator.email: "" > > # operator wallet address > operator.wallet: "" > > # operator wallet features > # operator.wallet-features: ["zksync"] > > # move pieces to trash upon deletion. Warning: if set to false, you risk disqualification for failed audits if a satellite database is restored from backup. > # pieces.delete-to-trash: true > > # file preallocated for uploading > # pieces.write-prealloc-size: 4.0 MiB > > # whether or not preflight check for database is enabled. > # preflight.database-check: true > > # whether or not preflight check for local system clock is enabled on the satellite side. When disabling this feature, your storagenode may not setup correctly. > # preflight.local-time-check: true > > # how many concurrent retain requests can be processed at the same time. > # retain.concurrency: 5 > > # allows for small differences in the satellite and storagenode clocks > # retain.max-time-skew: 72h0m0s > > # allows configuration to enable, disable, or test retain requests from the satellite. Options: (disabled/enabled/debug) > # retain.status: enabled > > # public address to listen on > server.address: :28967 > > # if true, client leaves may contain the most recent certificate revocation for the current certificate > # server.extensions.revocation: true > > # if true, client leaves must contain a valid "signed certificate extension" (NB: verified against certs in the peer ca whitelist; i.e. if true, a whitelist must be provided) > # server.extensions.whitelist-signed-leaf: false > > # path to the CA cert whitelist (peer identities must be signed by one these to be verified). this will override the default peer whitelist > # server.peer-ca-whitelist-path: "" > > # identity version(s) the server will be allowed to talk to > # server.peer-id-versions: latest > > # private address to listen on > server.private-address: 127.0.0.1:7778 > > # url for revocation database (e.g. bolt://some.db OR redis://127.0.0.1:6378?db=2&password=abc123) > # server.revocation-dburl: bolt://config/revocations.db > > # if true, uses peer ca whitelist checking > # server.use-peer-ca-whitelist: true > > # total allocated bandwidth in bytes (deprecated) > storage.allocated-bandwidth: 0 B > > # total allocated disk space in bytes > storage.allocated-disk-space: 2.00 TB > > # how frequently Kademlia bucket should be refreshed with node stats > # storage.k-bucket-refresh-interval: 1h0m0s > > # path to store data in > storage.path: /app/config/storage > > # a comma-separated list of approved satellite node urls (unused) > # storage.whitelisted-satellites: "" > > # how often the space used cache is synced to persistent storage > # storage2.cache-sync-interval: 1h0m0s > > # directory to store databases. if empty, uses data path > storage2.database-dir: /app/config/db > > # size of the piece delete queue > # storage2.delete-queue-size: 10000 > > # how many piece delete workers > # storage2.delete-workers: 1 > > # how soon before expiration date should things be considered expired > # storage2.expiration-grace-period: 48h0m0s > > # how many concurrent requests are allowed, before uploads are rejected. 0 represents unlimited. > # storage2.max-concurrent-requests: 0 > > # amount of memory allowed for used serials store - once surpassed, serials will be dropped at random > # storage2.max-used-serials-size: 1.00 MB > > # a client upload speed should not be lower than MinUploadSpeed in bytes-per-second (E.g: 1Mb), otherwise, it will be flagged as slow-connection and potentially be closed > # storage2.min-upload-speed: 0 B > > # if the portion defined by the total number of alive connection per MaxConcurrentRequest reaches this threshold, a slow upload client will no longer be monitored and flagged > # storage2.min-upload-speed-congestion-threshold: 0.8 > > # if MinUploadSpeed is configured, after a period of time after the client initiated the upload, the server will flag unusually slow upload client > # storage2.min-upload-speed-grace-duration: 10s > > # how frequently Kademlia bucket should be refreshed with node stats > # storage2.monitor.interval: 1h0m0s > > # how much bandwidth a node at minimum has to advertise (deprecated) > # storage2.monitor.minimum-bandwidth: 0 B > > # how much disk space a node at minimum has to advertise > # storage2.monitor.minimum-disk-space: 500.00 GB > > # how frequently to verify the location and readability of the storage directory > # storage2.monitor.verify-dir-readable-interval: 1m0s > > # how frequently to verify writability of storage directory > # storage2.monitor.verify-dir-writable-interval: 5m0s > > # how long after OrderLimit creation date are OrderLimits no longer accepted > # storage2.order-limit-grace-period: 1h0m0s > > # length of time to archive orders before deletion > # storage2.orders.archive-ttl: 168h0m0s > > # duration between archive cleanups > # storage2.orders.cleanup-interval: 5m0s > > # maximum duration to wait before trying to send orders > # storage2.orders.max-sleep: 30s > > # path to store order limit files in > storage2.orders.path: /app/config/orders > > # timeout for dialing satellite during sending orders > # storage2.orders.sender-dial-timeout: 1m0s > > # duration between sending > # storage2.orders.sender-interval: 1h0m0s > > # timeout for sending > # storage2.orders.sender-timeout: 1h0m0s > > # if set to true, all pieces disk usage is recalculated on startup > # storage2.piece-scan-on-startup: true > > # allows for small differences in the satellite and storagenode clocks > # storage2.retain-time-buffer: 48h0m0s > > # how long to spend waiting for a stream operation before canceling > # storage2.stream-operation-timeout: 30m0s > > # file path where trust lists should be cached > # storage2.trust.cache-path: config/trust-cache.json > > # list of trust exclusions > # storage2.trust.exclusions: "" > > # how often the trust pool should be refreshed > # storage2.trust.refresh-interval: 6h0m0s > > # list of trust sources > # storage2.trust.sources: https://www.storj.io/dcs-satellites > > # address for jaeger agent > # tracing.agent-addr: agent.tracing.datasci.storj.io:5775 > > # application name for tracing identification > # tracing.app: storagenode > > # application suffix > # tracing.app-suffix: -release > > # buffer size for collector batch packet size > # tracing.buffer-size: 0 > > # whether tracing collector is enabled > # tracing.enabled: true > > # how frequently to flush traces to tracing agent > # tracing.interval: 0s > > # buffer size for collector queue size > # tracing.queue-size: 0 > > # how frequent to sample traces > # tracing.sample: 0 > > # Interval to check the version > # version.check-interval: 15m0s > > # Request timeout for version checks > # version.request-timeout: 1m0s > > # server address to check its version against > version.server-address: https://version.storj.io > > ``` ---
**Author:** ![nerdatwork](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/nerdatwork/32/1135_2.png) [@nerdatwork](https://forum.storj.io/u/nerdatwork)\ **Post date:** [March 22, 2024, 7:32am UTC](https://forum.storj.io/t/invalid-configuration-file-key-and-moved-db-orders-and-logs/25604/2 "2024-03-22T07:32:21Z")
> [@CubeFan](#): > > I get “errors” I don’t see any error. Every log line is categorized as `INFO`. The lines that mention `Invalid ... key` can be ignored. It shows up as `config.yaml` is being used by 2 processes. ---
**Author:** ![CubeFan](https://storj.bcdn.literatehosting.com/letter_avatar/cubefan/32/5_5575768a8748004e209b776fc1b2916d.png) [@CubeFan](https://forum.storj.io/u/CubeFan)\ **Post date:** [March 22, 2024, 7:44am UTC](https://forum.storj.io/t/invalid-configuration-file-key-and-moved-db-orders-and-logs/25604/3 "2024-03-22T07:44:26Z")
That they are not real errors is true, that’s why I wrote it in “”. But for me Invalid means that something is not as it should be. I haven’t restarted my nodes for a long time. does that mean the entries are normal and I could use the configs like this? ---
**Author:** ![Alexey](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/alexey/32/41_2.png) [@Alexey](https://forum.storj.io/u/Alexey)\ **Post date:** [March 22, 2024, 8:02am UTC](https://forum.storj.io/t/invalid-configuration-file-key-and-moved-db-orders-and-logs/25604/4 "2024-03-22T08:02:14Z")
> [@CubeFan](#): > > `INFO Invalid configuration file key` since it’s `INFO`, it can be safely ignored. This is `storagenode-updater` complaining about not known to it keys (it shares the `config.yaml` file with `storagenode`). > [@CubeFan](#): > > does that mean the entries are normal and I could use the configs like this? yes But I would like to suggest to use a long format for the volumes, i.e. ```auto volumes: - type: bind source: "${NODE_DATA}" target: /app/config/storage - type: bind source: "${NODE_IDENTITY}" target: /app/identity - type: bind source: "${NODE_CONFIG}/config.yaml" target: /app/config/config.yaml - type: bind source: "${NODE_ORDERS}" target: /app/config/orders - type: bind source: "${NODE_DB}" target: /app/config/db - type: bind source: "${NODE_LOGS}" target: /app/config/logs ``` instead of this dangerous `-v` format (see [Volumes | Docker Docs](https://docs.docker.com/storage/volumes/#differences-between--v-and---mount-behavior)): > [@CubeFan](#): > > ```auto > volumes: > - "${NODE_DATA}:/app/config/storage" > - "${NODE_IDENTITY}:/app/identity" > - "${NODE_CONFIG}/config.yaml:/app/config/config.yaml" > - "${NODE_ORDERS}:/app/config/orders" > - "${NODE_DB}:/app/config/db" > - "${NODE_LOGS}:/app/config/logs" > > ``` and also perhaps special options you may specify right in the `docker-compose.yaml` instead of `config.yaml`, i.e. ```auto command: - --log.output="/app/config/logs/node.log" - --storage2.database-dir=/app/config/db - --storage2.orders.path=/app/config/orders ``` ---
**Author:** ![CubeFan](https://storj.bcdn.literatehosting.com/letter_avatar/cubefan/32/5_5575768a8748004e209b776fc1b2916d.png) [@CubeFan](https://forum.storj.io/u/CubeFan)\ **Post date:** [March 22, 2024, 8:46am UTC](https://forum.storj.io/t/invalid-configuration-file-key-and-moved-db-orders-and-logs/25604/5 "2024-03-22T08:46:06Z")
ok if I have understood you correctly, the compose should look like this? And in the config.yaml I take the entries out again? > **docker-compose.yaml** > > ```auto > version: "3" > services: > storj-node: > image: storjlabs/storagenode:latest > container_name: "storj-node${NODE_ID}" > restart: unless-stopped > stop_grace_period: 300s > ports: > - "140${NODE_ID}:14002/tcp" > - "289${NODE_ID}:28967/tcp" > - "289${NODE_ID}:28967/udp" > volumes: > - type: bind > source: "${NODE_DATA}" > target: /app/config/storage > - type: bind > source: "${NODE_IDENTITY}" > target: /app/identity > - type: bind > source: "${NODE_CONFIG}/config.yaml" > target: /app/config/config.yaml > - type: bind > source: "${NODE_ORDERS}" > target: /app/config/orders > - type: bind > source: "${NODE_DB}" > target: /app/config/db > - type: bind > source: "${NODE_LOGS}" > target: /app/config/logs > environment: > - "EMAIL=${NODE_EMAIL}" > - "ADDRESS=${NODE_EXTERNAL}" > - "STORAGE=${NODE_STORAGE}" > - "WALLET=${NODE_WALLET}" > - "SETUP=false" > - "AUTO_UPDATE=true" > command: > - --log.output="/app/config/logs/node.log" > - --storage2.database-dir=/app/config/db > - --storage2.orders.path=/app/config/orders > > ``` I didn’t understand the problem with the -v or -mount but if you say this way is better then I trust it. Then another quick question. I am currently migrating from windows to linux. do I also have to migrate the files revocations.db and trust-cache.json to the config folder? ---
**Author:** ![Alexey](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/alexey/32/41_2.png) [@Alexey](https://forum.storj.io/u/Alexey)\ **Post date:** [March 23, 2024, 9:35am UTC](https://forum.storj.io/t/invalid-configuration-file-key-and-moved-db-orders-and-logs/25604/6 "2024-03-23T09:35:15Z")
Yes, looks good. > [@CubeFan](#): > > do I also have to migrate the files revocations.db and trust-cache.json to the config folder? no. They will be re-created automatically.