Error #827
Comments
|
@intoro Sorry for this, we have been using "dev" branch and "master" was really behind. I have merged dev into master, so this should work now. Could you test again? |
|
@intoro That error message usually comes up for me when docker is out of date. Sous-Chef has been following the latest docker, and you really need to follow the install instructions, including those for docker-compose, which means adulterating your system with the Docker PPAs (or equivalent), in order to get the latest version. Sorry about that. |
|
Did you give up on trying it? |
|
No, Just Been Busy. I think I'll have time tonight. I'll Update You
…On Mar 4, 2018 6:27 PM, "Nick" ***@***.***> wrote:
Did you give up on trying it?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#827 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AXntFt_Umx75g5vgFJxHUYx5fkySLHaYks5tbKKLgaJpZM4R4Y-M>
.
|
|
Thanks. Take your time and don't get discouraged! We really appreciate the feedback. This software is deployed but it's definitely a beta thing, so we are hungry for data on how it goes for others. |
|
@intoro is this now fixed? |
Expected Behaviour
When I run:
docker-compose build
Actual Behaviour
ERROR: Version in "./docker-compose.yml" is unsupported. You might be seeing this error because you're using the wrong Compose file version. Either specify a version of "2" (or "2.0") and place your service definitions under the
serviceskey, or omit theversionkey and place your service definitions at the root of the file to use version 1.For more on the Compose file format versions, see https://docs.docker.com/compose/compose-file/
Steps to reproduce
The text was updated successfully, but these errors were encountered: