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
MSBuild failing to parse a valid compose file #98
Comments
I'm seeing the same issue on 2.1.300-preview2-008530 on windows. and Visual Studio 2017 15.7 preview 4. |
Same error here with the latest VS2017 preview (15.7.0 preview 5). |
I too had this problem. I was able to work around it by using the alternative environment notation: rabbitmq:
image: "rabbitmq:3.6-management-alpine"
platform: linux
environment:
RABBITMQ_ERLANG_COOKIE: "weeeeeeeeeeeeeeee"
RABBITMQ_DEFAULT_USER: "rabbitmq"
RABBITMQ_DEFAULT_PASS: "Password123!"
RABBITMQ_DEFAULT_VHOST: "/"
ports:
- "15672:15672"
- "5672:5672" |
This notation isn't working for me. I already tested it and I got the same error. |
Thanks for reporting. We are investigating the parsing issue in our tooling. I did find the alternative environment notation seemed to work as a workaround. @pellea, what is the error you see with the workaround? |
Try the following. This works for me. I think the underscores are causing the problem. mssql:
image: microsoft/mssql-server-linux:2017-latest
platform: linux
environment:
"ACCEPT_EULA": "Y"
"SA_PASSWORD": "${SA_Password}" |
@pellea one possible workaround you can try is to define those variables in |
My bad, the workaround works. I didn't remove the '-' before the line of each env key/value. |
I can confirm that the workaround works for me too. |
Same here, worked all fine until I installed VS 15.7.0 today. The notation from @KevM solved the issue. |
Same problem here with 15.7.1. Actually my docker-compose file is still in version 2 can that be the problem ? will try the workaround |
…specified in env var (#629) * Add Dockerfiles to the gateway and configuration services * Use more specific docker tags to avoid base images changing unexpectedly * Add Service Fabric deployment manifests and script * Don't use portability.dot.net as the default backend URI * For the time being, require the Portability Service URI to be specified explicitly, either with an environment variable or with a command line argument. * Once the new service backend is ready for general use, it can be the new default. * Replace DeploySF.bat with a more robust ps1 script * Move SF manifests out of /src (and into /deploy) * Use alternate docker-compose env var format to work around microsoft/DockerTools#98 * Add docker-compose targets * Only require -e for commands that make remote calls * Update apiport tests to include -e when necessary
* Add SF Mesh templates and deployment instructions * Add an SF Mesh template with both Linux and Windows containers * Use alternate docker-compose env var format to work around microsoft/DockerTools#98
Note: don't forget to put a space between keys and values:
No:
|
Running into this same issue but I am unsure how to convert nested variables into the working format.
Update: this worked after finding the right docs here
|
Also ran into this issue after VS2017 automatically updated my project. This worked before:
Changing to this fixed it:
|
@haniamr removing
from |
@prisar thanks for the confirmation, I'll be closing this issue since the fix is already in the latest public version. |
@haniamr This is an issue in VS 15.9.6 when using the same valid format for build arguments. Build:
In
The Should I make this a new issue? |
When I try to build a .dcproj I've recently started seeing this error:
The top part of the dockerfile is as follows:
Where the first element of the
environment
section is causing the problem.The docker-compose.yml file is perfectly fine and everything works as expected using
docker-compose up
P.S. I did recently install the latest
2.1.300-preview2-008533
dotnet core SDK, but I haven't uninstalled it yet to see if it is somehow causing the problem.The text was updated successfully, but these errors were encountered: