Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mapped folder remains empty for node #42

Open
dolphinkite opened this issue Jan 14, 2022 · 2 comments
Open

Mapped folder remains empty for node #42

dolphinkite opened this issue Jan 14, 2022 · 2 comments

Comments

@dolphinkite
Copy link

Hi,

I'm running this node on a Synology Docker (as described here: https://medium.com/decentralize-today/how-to-run-a-monero-node-on-a-synology-nas-3a3ed36bc3f8) but I am having a few issues:

When I look on the mapped drive, the folder is completely empty. I did use the parameter: -v /volume1/docker/MyNode:/home/.bitmonero

When I go to /volume1/docker/MyNode there is absolutely nothing. However, if I attach to the Docker process using: docker exec -ti MyNode bash I am able to see that there are various files, in 5GB file (although this has been running for 5 days. It should only have taken an hour or so do download the whole DB so I don't understand that part either).

Is there an explanation why I can't see the files on my mapped drive? I assume this is related to the fact that the container runs under the monero user?

My concern is that if I need to update the container by deleting it and re-running it, I'll lose the DB. From the looks of it, it will take me a couple of weeks to build the DB, which also doesn't make any sense. Any possible explanation on that?

Thanks

@samturner3
Copy link

I have this issue also, even when ssh as root ls -las shows nothing, yet when I stop and restart the docker image the console picks up syncing from where it left off, so must be saving somewhere...

@teambvd
Copy link

teambvd commented May 15, 2022

I have this issue also, even when ssh as root ls -las shows nothing, yet when I stop and restart the docker image the console picks up syncing from where it left off, so must be saving somewhere...

@samturner3 Assuming you've your volume mappings the same as what's initially referenced above, it's currently saving within the docker image file - you've likely seen it grow over time as the daemon runs

When I look on the mapped drive, the folder is completely empty. I did use the parameter: -v /volume1/docker/MyNode:/home/.bitmonero

When I go to /volume1/docker/MyNode there is absolutely nothing

@dolphinkite the mapping's unfortunately incorrect here (referring to the outline here)- homedirs follow a format of /home/<user>/<usersFolders>. In your case, it'd look like:

-v /volume1/docker/MyNode/monero-data:/home/monero/.bitmonero

What I'd probably do though is set up a config file instead, and point the .bitmonero folder wherever you'd like with that, along with setting up your peer and rate limits all in one. Have that file as /volume1/docker/MyNode/bitmonero.conf so it's persistent as well.

Been a while, and I know it's likely you've both got it sorted by now, but figured I'd post this up in case someone else comes along 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants