Any chance of a make-less compose? (TrueNAS support)

[Soukyuu]

Have you read a contributing guide?

• I have read CONTRIBUTING.md
• I have searched the existing requests and didn't find any that were similar
• I have considered creating a pull request instead and want to proceed

Clear and concise description of the problem

It is currently impossible to run any-sync on a trueNAS despite docker support, because trueNAS is not providing make/git packages. The only workaround is to actually create a VM on trueNAS and install a whole OS just to run any-sync, which is rather overkill.

Suggested solution

I have no idea why make is required to set up, and am also a docker noob, so I have no idea about how a solution could be implemented.

Alternative

No response

Additional context

No response

[mighty-sponge]

Hi! If you're using pure Docker and Compose, you can do the following:

1. Building an image to generate a configuration:
   docker buildx build --load --tag generateconfig-env --file Dockerfile-generateconfig-env .
2. Run a container from this image and get the configuration (one-time run):
   docker run --rm --volume ${CURDIR}/:/code/ generateconfig-env
3. Now you can start any-sync!
   docker compose up -d

[Soukyuu]

Hi and thank you for replying! This looks promising.

I managed to execute the first step and it seems to have finished with a warning, but nothing that should stop it from working:

root@Hydra[/mnt/vault/docker/anysync]# docker buildx build --load --tag generateconfig-env --file Dockerfile-generateconfig-env .
[+] Building 24.0s (11/11) FINISHED                                                                                                              docker:default
 => [internal] load build definition from Dockerfile-generateconfig-env                                                                                    0.4s
 => => transferring dockerfile: 286B                                                                                                                       0.0s
 => resolve image config for docker-image://docker.io/docker/dockerfile:1                                                                                  1.8s
 => docker-image://docker.io/docker/dockerfile:1@sha256:b6afd42430b15f2d2a4c5a02b919e98a525b785b1aaff16747d2f623364e39b6                                   2.6s
 => => resolve docker.io/docker/dockerfile:1@sha256:b6afd42430b15f2d2a4c5a02b919e98a525b785b1aaff16747d2f623364e39b6                                       0.2s
 => => sha256:77246a01651da592b7bae79e0e20ed3b4f2e4c00a1b54b7c921c91ae3fa9ef07 13.57MB / 13.57MB                                                           1.7s
 => => sha256:b6afd42430b15f2d2a4c5a02b919e98a525b785b1aaff16747d2f623364e39b6 8.40kB / 8.40kB                                                             0.0s
 => => sha256:62b0eac4b38b65f257ba2525a1bc87978b5e339d6133b5daef1bde40fe7aa10f 850B / 850B                                                                 0.0s
 => => sha256:6742480c08d7878bbb82a5f5b55d7cb17c5dea60d2068cb2bd37994f3a5c680e 1.33kB / 1.33kB                                                             0.0s
 => => extracting sha256:77246a01651da592b7bae79e0e20ed3b4f2e4c00a1b54b7c921c91ae3fa9ef07                                                                  0.1s
 => [internal] load metadata for docker.io/library/python:3.11-alpine                                                                                      1.9s
 => [internal] load .dockerignore                                                                                                                          0.2s
 => => transferring context: 2B                                                                                                                            0.0s
 => [1/4] FROM docker.io/library/python:3.11-alpine@sha256:610ede222c1fa9675c694c99429f8d2c1b4e243f1982246da9e540eb5800ee4a                                4.4s
 => => resolve docker.io/library/python:3.11-alpine@sha256:610ede222c1fa9675c694c99429f8d2c1b4e243f1982246da9e540eb5800ee4a                                0.2s
 => => sha256:610ede222c1fa9675c694c99429f8d2c1b4e243f1982246da9e540eb5800ee4a 10.30kB / 10.30kB                                                           0.0s
 => => sha256:5608f9b48d9f51c4d327adc10ba1720f1e03763abe4e146dd022f381a8349b16 1.74kB / 1.74kB                                                             0.0s
 => => sha256:e7d35dbf6dd2e3cf262956100b233a4f46f7e21bc05c0e2028d1eace7fee5e2b 5.15kB / 5.15kB                                                             0.0s
 => => sha256:d6919b1d38e53ccdc8cbb29e0abc43a8479d26bda83c438c3d88edfed60f3372 456.92kB / 456.92kB                                                         0.5s
 => => sha256:bc0e8b3a76b969eeb85ccd0bbe2839393956c01e00a5ea44df7183c845b62eb5 246B / 246B                                                                 0.6s
 => => sha256:2216f72b503965e0d6f92753a108881bc06183c9d93e0c1fae45692622df1a1f 15.95MB / 15.95MB                                                           2.2s
 => => extracting sha256:d6919b1d38e53ccdc8cbb29e0abc43a8479d26bda83c438c3d88edfed60f3372                                                                  0.1s
 => => extracting sha256:2216f72b503965e0d6f92753a108881bc06183c9d93e0c1fae45692622df1a1f                                                                  0.5s
 => => extracting sha256:bc0e8b3a76b969eeb85ccd0bbe2839393956c01e00a5ea44df7183c845b62eb5                                                                  0.0s
 => [internal] load build context                                                                                                                          0.4s
 => => transferring context: 131B                                                                                                                          0.0s
 => [2/4] WORKDIR /code                                                                                                                                    0.7s
 => [3/4] COPY docker-generateconfig/env-requirements.txt requirements.txt                                                                                 0.4s
 => [4/4] RUN pip install -r requirements.txt                                                                                                              9.6s
 => exporting to image                                                                                                                                     0.7s 
 => => exporting layers                                                                                                                                    0.5s 
 => => writing image sha256:a6551af15993b1b9cc6899e868d59ceb6b53935fb9e7b5c9eb0cee439a8e0875                                                               0.0s 
 => => naming to docker.io/library/generateconfig-env
WARNING: current commit information was not captured by the build: failed to read current commit information with git rev-parse --is-inside-work-tree

However the next step fails:

root@Hydra[/mnt/vault/docker/anysync]# docker run --rm --volume ${CURDIR}/:/code/ generateconfig-env
python: can't open file '/code/docker-generateconfig/env.py': [Errno 2] No such file or directory

Contents of my directory:

root@Hydra[/mnt/vault/docker/anysync]# ls
CHANGELOG.md                       Dockerfile-generateconfig-processing  docker-compose.any-sync-consensusnode.yml  docker-compose.any-sync-node-all.yml
Dockerfile                         LICENSE.md                            docker-compose.any-sync-coordinator.yml    docker-compose.yml
Dockerfile-generateconfig-anyconf  Makefile                              docker-compose.any-sync-filenode.yml       docker-generateconfig
Dockerfile-generateconfig-env      README.md                             docker-compose.any-sync-node-1.yml         tests

What did I do wrong?

[Soukyuu]

Hmm I do have a docker-generateconfig subdir with the following content, so it should be correct if I'm reading the command line for the second step correctly, weird:

truenas_admin@Hydra[/mnt/vault/docker/anysync]$ ls docker-generateconfig 
anyconf.sh  env-requirements.txt  env.py  etc  processing.sh  setListenIp.py

[Soukyuu]

Ah, ok. I assumed ${CURDIR} to be popluated, it was not. Changing the command to

docker run --rm --volume ./:/code/ generateconfig-env

Made it run. The third step also ran fine, it still fails to start but that's because of a configuration issue which is unrelated.

Thank you very much for the hint, maybe it's a good idea to add the alternative to the documentation?

[Soukyuu]

For those who land here, make sure to run the second command every time you edit your env.override

[fb929]

here’s an instruction on how to run self-host without make
https://github.com/anyproto/any-sync-dockercompose/wiki/Usage#run-docker-compose