Mix.Project error

[felipereigosa]

I cannot seem to get this working. As far as I can tell all the dependencies are installed correctly but I get this error on bin/init, any help would be very appreciated.

Cloning source repositories

fatal: destination path '/home/felipe/Desktop/hubs-compose/services/reticulum' already exists and is not an empty directory. fatal: destination path '/home/felipe/Desktop/hubs-compose/services/dialog' already exists and is not an empty directory. fatal: destination path '/home/felipe/Desktop/hubs-compose/services/hubs' already exists and is not an empty directory. fatal: destination path '/home/felipe/Desktop/hubs-compose/services/spoke' already exists and is not an empty directory.

Initializing Reticulum

/snap/docker/2746/lib/python3.6/site-packages/paramiko/transport.py:32: CryptographyDeprecationWarning: Python 3.6 is no longer supported by the Python core team. Therefore, support for it is deprecated in cryptography. The next release of cryptography (40.0) will be the last to support Python 3.6. from cryptography.hazmat.backends import default_backend Building reticulum Sending build context to Docker daemon 23.62MB Step 1/12 : ARG ALPINE_VERSION=3.16.2 Step 2/12 : ARG ELIXIR_VERSION=1.14.3 Step 3/12 : ARG ERLANG_VERSION=23.3.4.18 Step 4/12 : FROM hexpm/elixir:${ELIXIR_VERSION}-erlang-${ERLANG_VERSION}-alpine-${ALPINE_VERSION} AS base ---> 4c457c0b83a2 Step 5/12 : RUN mix do local.hex --force, local.rebar --force ---> Using cache ---> bf2e90779e64 Step 6/12 : FROM base AS dev ---> bf2e90779e64 Step 7/12 : RUN apk add --no-cache git inotify-tools ---> Using cache ---> 0673bb0c0fa0 Step 8/12 : COPY container/dev-perms.pem /etc/perms.pem ---> Using cache ---> 1cac6a1a9655 Step 9/12 : COPY container/trapped-mix /usr/local/bin/trapped-mix ---> Using cache ---> 7baa39b39a4d Step 10/12 : WORKDIR /code ---> Using cache ---> 9cec0cf6f9b5 Step 11/12 : HEALTHCHECK CMD wget --no-check-certificate --no-verbose --tries=1 --spider https://localhost:4000/stream-offline.png ---> Using cache ---> b3953713131a Step 12/12 : CMD sh -c "PERMS_KEY=\"$(cat /etc/perms.pem)\" mix phx.server" ---> Using cache ---> b341cb77d371 Successfully built b341cb77d371 Successfully tagged hubs-compose_reticulum:latest [+] Running 1/0 ⠿ Container hubs-compose-mutagen-1 Running 0.0s [+] Running 1/0 ⠿ Container hubs-compose-db-1 Created 0.0s [+] Running 1/1 ⠿ Container hubs-compose-mutagen-1 Healthy 0.5s [+] Running 1/1 ⠿ Container hubs-compose-db-1 Started 0.3s ** (Mix) Could not find a Mix.Project, please ensure you are running Mix in a directory with a mix.exs file [+] Running 1/3 ⠿ Container hubs-compose-mutagen-1 Error while Stopping 0.0s ⠿ Container hubs-compose-db-1 Removed 0.3s ⠿ Mutagen Error: unable to connect to Mutagen daemon: client/daemon version mismatch (daemon restart recommended) 0.0s unable to pause Mutagen sessions: unable to connect to Mutagen daemon: client/daemon version mismatch (daemon restart recommended)

[tobias-weiss-ai-xr]

Replacing the mutagen and mutagen-compose binaries with the latest release from the website solved the problem for me (on arch linux).

https://github.com/mutagen-io/mutagen/releases

[truedat101]

Because this mutagen tool doesn't have a set installer on Linux (unless someone provides a package installer), you probably will hit some stumbling blocks here. As a devops person, I come from the house of lazy, do less approach, and manual installs really bug me. I found out that putting mutagen into my ~/bin didn't work, but putting it into /usr/local/bin did work. Also note, your user used for the installation will possibly need special permissions to access docker.