You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The installation method I used is docker installation.When I run “docker-compose build”
the error message is that:
--RUN make:
Stack no longer supports Cabal version below 1.19.2 but version 1.18.1.5 was found.
I think the version that the stack.yaml specifing is not the latest so I add a command “resolver: ghc-8.6.5 ”。
After that,in the process of make,the ghc-8.6.5 has been installed ,but the error is there are some package dependencies were wrong(so many)like "In the dependencies for snap-1.1.2.0:
attoparsec must match >=0.10 && <0.14, but the stack configuration has no specified version
(latest matching version is 0.13.2.2)"。
I am a newbie with docker, how can I solve this problem and let the software start smoothly?
Environment:
windows 10
CPU:x64
virtualbox:6.0.6
fedora:30
Docker version 18.06.3-ce, build d7080c1
docker-compose version 1.22.0, build f46880f
The text was updated successfully, but these errors were encountered:
The installation method I used is docker installation.When I run “docker-compose build”
the error message is that:
--RUN make:
Stack no longer supports Cabal version below 1.19.2 but version 1.18.1.5 was found.
I think the version that the stack.yaml specifing is not the latest so I add a command “resolver: ghc-8.6.5 ”。
After that,in the process of make,the ghc-8.6.5 has been installed ,but the error is there are some package dependencies were wrong(so many)like "In the dependencies for snap-1.1.2.0:
attoparsec must match >=0.10 && <0.14, but the stack configuration has no specified version
(latest matching version is 0.13.2.2)"。
I am a newbie with docker, how can I solve this problem and let the software start smoothly?
Environment:
windows 10
CPU:x64
virtualbox:6.0.6
fedora:30
Docker version 18.06.3-ce, build d7080c1
docker-compose version 1.22.0, build f46880f
The text was updated successfully, but these errors were encountered: