Core DAppNode Packages versions
- bind.dnp.dappnode.eth: 0.2.6
- core.dnp.dappnode.eth: 0.2.58
- dappmanager.dnp.dappnode.eth: 0.2.53, branch: develop, commit: 45ec898e
- https.dnp.dappnode.eth: 0.1.3
- ipfs.dnp.dappnode.eth: 0.2.18
- wifi.dnp.dappnode.eth: 0.2.8
- wireguard.dnp.dappnode.eth: 0.1.1
System info
- dockerComposeVersion: 1.25.5
- dockerServerVersion: 20.10.6
- dockerCliVersion: 20.10.6
- os: debian
- versionCodename: bullseye
- architecture: amd64
- kernel: 5.10.0-14-amd64
- Disk usage: 47%
Hello,
Ever since the 0.1.3 release of Web3Signer was pushed out, I have been unable to update to it. One strange thing I’ve noticed is that the package size shows as “0”. A few minutes after clicking the “Update” button on the package, the following log is written:
error Call to packageInstall
Reply: Command failed: docker-compose -f /usr/src/app/dnp_repo/web3signer.dnp.dappnode.eth/docker-compose.yml up --no-start --remove-orphans <&- Error response from daemon: readlink /var/lib/docker/overlay2: invalid argument
Error: Command failed: docker-compose -f /usr/src/app/dnp_repo/web3signer.dnp.dappnode.eth/docker-compose.yml up --no-start --remove-orphans <&-
Error response from daemon: readlink /var/lib/docker/overlay2: invalid argumentat /usr/src/app/webpack:/@dappnode/dappmanager/src/utils/shell.ts:35:16 at Generator.throw (<anonymous>) at rejected (/usr/src/app/index.js:400143:65) at runMicrotasks (<anonymous>) at processTicksAndRejections (node:internal/process/task_queues:96:5)
{
“name”: “web3signer.dnp.dappnode.eth”,
“version”: “0.1.3”,
“userSettings”: {},
“options”: {}
}
Has anyone else run into this?