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

Errors on elm-test #1

Open
tasuki opened this issue Mar 27, 2021 · 2 comments
Open

Errors on elm-test #1

tasuki opened this issue Mar 27, 2021 · 2 comments

Comments

@tasuki
Copy link

tasuki commented Mar 27, 2021

On a project of mine:

$ alias elm-test='docker run --rm --entrypoint "elm-test" -v `pwd`:/workdir -v `pwd`/.elm:/.elm -w /workdir -e http_proxy -e https_proxy semenovp/tiny-elm:all-latest'
$ elm-test
Downloading elm-json 0%
Failed to download:
< https://github.com/zwilias/elm-json/releases/download/v0.2.10/elm-json-v0.2.10-x86_64-unknown-linux-musl.tar.gz
> /.elm/elm-tooling/elm-json/0.2.10/elm-json
tar must be installed on your system and be in $PATH:
spawn tar ENOENT

When I put the elm-json from that url into .elm/elm-tooling/elm-json/0.2.10/elm-json I get:

$ elm-test
Solving dependencies > Compiling > Starting tests
Error: listen EACCES: permission denied /tmp/elm_test-1.sock
    at Server.setupListenHandle [as _listen2] (node:net:1293:21)
    at listenInCluster (node:net:1358:12)
    at Server.listen (node:net:1456:5)
    at /usr/local/lib/node_modules/elm-test/lib/Supervisor.js:266:12
    at new Promise (<anonymous>)
    at Object.run (/usr/local/lib/node_modules/elm-test/lib/Supervisor.js:19:10)
    at run (/usr/local/lib/node_modules/elm-test/lib/RunTests.js:245:31)
    at processTicksAndRejections (node:internal/process/task_queues:94:5)

🤷

@piotr-semenov
Copy link
Owner

piotr-semenov commented Mar 29, 2021

Hi @tasuki!
Can you please share your elm.json and tests? I am not a real Elm developer, so your project will be very helpful to resolve the second part of your issue.
First part of your issue is clear to me. And a single line edit to Dockerfile will fix it.

@tasuki
Copy link
Author

tasuki commented Apr 2, 2021

@piotr-semenov thank you for your quick reply! And for dockerizing Elm development! (I see my initial issue looks a bit... curt? It wasn't meant that way!)

The elm.json this happened on was this one, I think. Fwiw I don't have a pressing need to get this resolved, just wanted to let you know 🙂

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

2 participants