Thanks!! I’d looked in the forum but hadn’t found that link.
1 Like
Having trouble with router bandwidth being chocked whenever Formicaio nodes are running, very chocked.
Also, last update seems to have broken it completely.
(Would send more in DM but your profile is hidden so I can’t.)
Yes, latest safenode binary needs more resources (including net bandwidth apparently) than previous versions, you’ll have to reduce the number of nodes you’re running.
3 Likes
hmm, tried to deploy it on docker in synology but getting an error:
docker-compose.yml file is invalid?
EDIT 1 not strong at this, but found out that docker already assumes there is an image and docker compose makes an image. So i ran docker-compose instead but still getting issues:
EDIT 2 created the folders myself and it seems to be running now. I see that I can add nodes to it. I have another server with more storage, can I add that storage somehow?
2 Likes
I honestly don’t know how synology works, but the data stored by each individual node will be stored wherever the synology docker engine stores the data for the containers it runs, i.e. its set root dir. It normally is set by default to /var/lib/docker, but you should be able to confirm the docker engine’s root dir with this command:
$ docker info | grep "Docker Root Dir"
Thus, if the storage you add/mount counts for that path too, then you should be able to use it for more nodes I’d imagine. Each node you create is a new container running in the docker engine, so it will use more storage under /var/lib/docker (or whichever path is set as the docker root dir). Otherwise, you can also change the docker engine’s root dir to any path you need it to be.
1 Like
interesting… i’ll have a look if I can set that somewhere/somehow
1 Like
In your case, if you ended up running it with docker compose as it seems, then all data will be stored wherever that docker_volumes folder is located, from your screenshot it seems to be at /volume1/docker/appdata/formicaio/deploy/local/docker_volumes. So you can add/mount more storage to that path and it should be usable I guess.
Not sure I’m completely following.
/volume1/docker/appdata/formicaio/deploy/local/docker_volumes
is one of the volumes that docker is storing right. i cannot add a volume to a folder. I think I need to add a volume to the container so it has multiple volumes right? (the volume I want to use is on another syno server (and thus different ip address).
Can’t run docker on the other syno as it isn’t supported (its an old model)
I see, perhaps you can run a second instance of formicaio on a separate volume…? (I may not make sense, this is due to my lack of knowledge of syno).
Basically when you run formicaio with docker compose, if it’s running as expected, it will run docker-in-docker, i.e. it will run a formicaio app container plus a docker engine container which is exclusively used by formicaio app and the nodes it instantiates. In such a scenario, this docker will store all the data within the docker_volumes/docker folder, which is located in the same folder you ran docker compose from. There many other way this could be configured, but that’s what the docker-compose.yml file is configure to do.
Formicaio at the moment doesn’t allow you to choose different paths for different nodes, but you should be able to run a second instance on a second syno volume…? i.e. run docker compose again from let’s say /volume2/docker/appdata/formicaio/deploy/local …? (again, I’m guessing here, not sure what’s the best way this fits within syno architecture).
2 Likes
I was able to mount the drive! I got it mounted in a seperate folder under:
/docker/appdata/formicaio/deploy/local/docker_volumes/docker/diskstation1
so that should be ok now right?
By the way, i have the nodes running for about 15 hours now but no rewards yet. Not sure how fast we should receive some rewards. I checked the logs but see a lot of errors as well
1 Like
I’m pretty sure (someone correct me if I’m wrong here) that uploads have stopped until update that is supposed to be happening today.
4 Likes
hmm…I don’t think it will be using it, I imagine that if you mounted it at /docker/appdata/formicaio/deploy/local/docker_volumes instead (i.e. no docker/diskstation1 in the path), and re-start the app with docker-compose down followed by docker-compose up, in that case it may work and all data ends up stored on that mounted disk, …not sure, you’ll have to play with it and give it a try to be sure. You can always confirm by checking if files are being created/stored on the mounted drive.
1 Like
problem is that you cannot mount to a non-empty folder. Given that docker_volumes already has subfolders, you can’t mount a drive to it 
Perhaps…, stop the app with docker compose down, then remove the docker_volumes folder entirely, then mount your volume onto that path, and finally start the app as you’ve done it the first time with docker compose up…you’ll loose everything you have at the moment (I mean formicaio nodes you’ve created), but perhaps worth a try.
2 Likes
I think you could copy contents out to make folder empty, mount the drive to it, and copy data back (it will be copied to new drive), and then start the nods
3 Likes
it took some time to get that working (the syno was not to happy about deleting the folder)
anyways, i have the image up and running with docker_volumes now mounting to the other synology. However, I seem to have a problem with starting the nodes. Getting message:
error running server function: Docker server error: Cannot update container f69889d4a50f9ce6358e353aab55408cfba5af2b2aeec0dc6c0edc91b4a67c2b: cannot update a stopped container: unknown
not sure what container he is referring to as both containers are up and running. when I retry to start the node I get:
error running server function: Docker server error: failed to create task for container: failed to start shim: mkdir /data/exec/containerd/daemon/io.containerd.runtime.v2.task/moby/f69889d4a50f9ce6358e353aab55408cfba5af2b2aeec0dc6c0edc91b4a67c2b: file exists: unknown
I was thinking, my older synology does not support BTRFS (its a ds213+). I’m assuming that is the reason? If so, is this related to autonomi itself or to the image?
That’s an error from the docker engine itself, the one running exclusively for formicaio launched by the docker-compose file.
It sounds to me it doesn’t like the old files (by saying file exists) and it’s getting confused with its own way of tracking its own tasks, or something like it, I’m just guessing. I think you may wanna clean up the docker_volumes folder and start fresh. If it was actually empty, then maybe is the FS issue you are mentioning, but not sure tbh.
tried a clean install again, but it has to do with the BTRFS format as it is still giving the same errors unfortunately.
Shame I can’t use my old syno
1 Like
There must be a way to do it, but you’ll have to dig in a bit around docker volumes/mounting opts, e.g. these folks seem to be talking of some similar setup with NFS so perhaps it’s an option for your scenario: How to directly mount NFS share/volume in container using docker compose v3 - Stack Overflow
probably, but I think it is more with the fact that BTRFS is not supported by the old synology. So, as I see it, data is stored in subvolumes on BTRFS, but if the old one does not support it, i am assuming it will error out.
Otherwise connecting external storage would not be possible. How would it work on RPI? only use the microsd for storage?