Closed oyren closed 3 years ago
You go to the trouble of creating a Issue and the next moment you find the solution ;). At least now I'm getting a permission error.
What fixed the error above was the following pull request https://github.com/gohornet/hornet/pull/1060
So the /app/ in my Docker compose file was too much.
New docker-compose.yml:
version: '3.3'
services:
hornet:
container_name: iota_hornet
image: gohornet/hornet:latest
volumes:
- ./config.json:/config.json:ro
- ./peering.json:/peering.json
- ./mainnetdb:/mainnetdb
- ./snapshots/mainnet:/snapshots/mainnet
restart: unless-stopped
network_mode: "host"
cap_drop:
- ALL
Ok nope permission error fixed and have the error from above again.
iota_hornet | 2021-04-29T09:05:50Z PANIC Snapshot snapshot/core.go:162 no download URL specified for snapshot files in config
@legacycode
I also had the same problem as OP, so I implemented your commits but now I am getting a mainenetdb permission denied. I tried it with both 39999 and 65532
Same with 39999
Yes the same problem mainnetdb/LOCK: Permission denied
was my permission problem from above, I had workaround it by giving the folders all rights (chmod 777 -R folder/filename).
There are more than one issues with the docker file. I am working on a fix. You can try my feature branch at: https://github.com/legacycode/hornet/tree/fix-docker and check if it solves the issues. I will create a PR in a few hours.
I will look into it, thanks. Could you please clarify that
mkdir mainnetdb && sudo chown 39999:39999 mainnetdb
mkdir -p snapshots/mainnet && sudo chown 39999:39999 snapshots -R
is correct?
@oyren Please have a look at #1068. I have documented the steps to check my PR. Please comment directly in the PR, if you find any issues in my solution. Thanks and best regards.
With your adjustments @legacycode I have version 1.0.1 running now, thanks. I will leave the Issue open until it is merged.
@legacycode I'm not sure if this is related, but I always get a new peeringid after docker-compose down
& docker-compose up
.
@oyren create a different issue for that :) that's another problem we also need to fix in the hornet code itself and the docker file.
@legacycode thank you for your help with this issue!