ERROR: The Compose file './docker-compose.yaml' is invalid because: contains unsupported option: 'labels'
I recently installed docker and was playing around docker compose.
$ docker-compose --version
docker-compose version 1.23.2, build 1110ad01
$ docker --version
Docker version 18.09.1, build 4c52b90
docker-compose.yaml contents:
services:
code:
image: code
build:
context: ../../../
labels:
build-date: "Wed Jan 16 21:36:30 UTC 2019"
git-commit: "abcd036f79e169c9df6b60d11ef5a105e020918d"
git-branch: "master"
git-repository: "shaml"
ecr-repository: "code"
build-tag: "latest"
dockerfile: ./deploy/Dockerfile
When I am labeling my docker image via docker-compose it's throwing me an error. I followed the syntax from https://docs.docker.com/compose/compose-file/#labels.
I am getting the following error when I am trying to run
docker-compose build
ERROR: The Compose file './docker-compose.yaml' is invalid because:
code-build contains unsupported option: 'labels'
I tried upgrading the docker and docker-compose version but seems like I do have the updated version.
Please help
upgrade docker build label
asked Jan 16 at 23:45
jarutojaruto
82
add a comment |
I recently installed docker and was playing around docker compose.
$ docker-compose --version
docker-compose version 1.23.2, build 1110ad01
$ docker --version
Docker version 18.09.1, build 4c52b90
docker-compose.yaml contents:
services:
code:
image: code
build:
context: ../../../
labels:
build-date: "Wed Jan 16 21:36:30 UTC 2019"
git-commit: "abcd036f79e169c9df6b60d11ef5a105e020918d"
git-branch: "master"
git-repository: "shaml"
ecr-repository: "code"
build-tag: "latest"
dockerfile: ./deploy/Dockerfile
When I am labeling my docker image via docker-compose it's throwing me an error. I followed the syntax from https://docs.docker.com/compose/compose-file/#labels.
I am getting the following error when I am trying to run
docker-compose build
ERROR: The Compose file './docker-compose.yaml' is invalid because:
code-build contains unsupported option: 'labels'
I tried upgrading the docker and docker-compose version but seems like I do have the updated version.
Please help
upgrade docker build label
asked Jan 16 at 23:45
jarutojaruto
82
add a comment |
I recently installed docker and was playing around docker compose.
$ docker-compose --version
docker-compose version 1.23.2, build 1110ad01
$ docker --version
Docker version 18.09.1, build 4c52b90
docker-compose.yaml contents:
services:
code:
image: code
build:
context: ../../../
labels:
build-date: "Wed Jan 16 21:36:30 UTC 2019"
git-commit: "abcd036f79e169c9df6b60d11ef5a105e020918d"
git-branch: "master"
git-repository: "shaml"
ecr-repository: "code"
build-tag: "latest"
dockerfile: ./deploy/Dockerfile
When I am labeling my docker image via docker-compose it's throwing me an error. I followed the syntax from https://docs.docker.com/compose/compose-file/#labels.
I am getting the following error when I am trying to run
docker-compose build
ERROR: The Compose file './docker-compose.yaml' is invalid because:
code-build contains unsupported option: 'labels'
I tried upgrading the docker and docker-compose version but seems like I do have the updated version.
Please help
upgrade docker build label
asked Jan 16 at 23:45
jarutojaruto
82
I recently installed docker and was playing around docker compose.
$ docker-compose --version
docker-compose version 1.23.2, build 1110ad01
$ docker --version
Docker version 18.09.1, build 4c52b90
docker-compose.yaml contents:
services:
code:
image: code
build:
context: ../../../
labels:
build-date: "Wed Jan 16 21:36:30 UTC 2019"
git-commit: "abcd036f79e169c9df6b60d11ef5a105e020918d"
git-branch: "master"
git-repository: "shaml"
ecr-repository: "code"
build-tag: "latest"
dockerfile: ./deploy/Dockerfile
When I am labeling my docker image via docker-compose it's throwing me an error. I followed the syntax from https://docs.docker.com/compose/compose-file/#labels.
I am getting the following error when I am trying to run
docker-compose build
ERROR: The Compose file './docker-compose.yaml' is invalid because:
code-build contains unsupported option: 'labels'
I tried upgrading the docker and docker-compose version but seems like I do have the updated version.
Please help
upgrade docker build label
upgrade docker build label
asked Jan 16 at 23:45
jarutojaruto
82
asked Jan 16 at 23:45
jarutojaruto
82
asked Jan 16 at 23:45
jarutojaruto
82
asked Jan 16 at 23:45
jarutojaruto
82
asked Jan 16 at 23:45
jarutojaruto
82
82
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
If you do not specify a version number, compose will default to a deprecated version 1 format. You also need to fix the indentation on the services section (it should not be at the same level as the services it contains, and it cannot be empty).
version: '3'
services:
code:
image: code
build:
context: ../../../
labels:
build-date: "Wed Jan 16 21:36:30 UTC 2019"
git-commit: "abcd036f79e169c9df6b60d11ef5a105e020918d"
git-branch: "master"
git-repository: "shaml"
ecr-repository: "code"
build-tag: "latest"
dockerfile: ./deploy/Dockerfile
answered Jan 18 at 15:34
BMitchBMitch
1785
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1395164%2ferror-the-compose-file-docker-compose-yaml-is-invalid-because-contains-uns%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
If you do not specify a version number, compose will default to a deprecated version 1 format. You also need to fix the indentation on the services section (it should not be at the same level as the services it contains, and it cannot be empty).
version: '3'
services:
code:
image: code
build:
context: ../../../
labels:
build-date: "Wed Jan 16 21:36:30 UTC 2019"
git-commit: "abcd036f79e169c9df6b60d11ef5a105e020918d"
git-branch: "master"
git-repository: "shaml"
ecr-repository: "code"
build-tag: "latest"
dockerfile: ./deploy/Dockerfile
answered Jan 18 at 15:34
BMitchBMitch
1785
add a comment |
If you do not specify a version number, compose will default to a deprecated version 1 format. You also need to fix the indentation on the services section (it should not be at the same level as the services it contains, and it cannot be empty).
version: '3'
services:
code:
image: code
build:
context: ../../../
labels:
build-date: "Wed Jan 16 21:36:30 UTC 2019"
git-commit: "abcd036f79e169c9df6b60d11ef5a105e020918d"
git-branch: "master"
git-repository: "shaml"
ecr-repository: "code"
build-tag: "latest"
dockerfile: ./deploy/Dockerfile
answered Jan 18 at 15:34
BMitchBMitch
1785
add a comment |
If you do not specify a version number, compose will default to a deprecated version 1 format. You also need to fix the indentation on the services section (it should not be at the same level as the services it contains, and it cannot be empty).
version: '3'
services:
code:
image: code
build:
context: ../../../
labels:
build-date: "Wed Jan 16 21:36:30 UTC 2019"
git-commit: "abcd036f79e169c9df6b60d11ef5a105e020918d"
git-branch: "master"
git-repository: "shaml"
ecr-repository: "code"
build-tag: "latest"
dockerfile: ./deploy/Dockerfile
answered Jan 18 at 15:34
BMitchBMitch
1785
If you do not specify a version number, compose will default to a deprecated version 1 format. You also need to fix the indentation on the services section (it should not be at the same level as the services it contains, and it cannot be empty).
version: '3'
services:
code:
image: code
build:
context: ../../../
labels:
build-date: "Wed Jan 16 21:36:30 UTC 2019"
git-commit: "abcd036f79e169c9df6b60d11ef5a105e020918d"
git-branch: "master"
git-repository: "shaml"
ecr-repository: "code"
build-tag: "latest"
dockerfile: ./deploy/Dockerfile
answered Jan 18 at 15:34
BMitchBMitch
1785
answered Jan 18 at 15:34
BMitchBMitch
1785
answered Jan 18 at 15:34
BMitchBMitch
1785
answered Jan 18 at 15:34
BMitchBMitch
1785
1785
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1395164%2ferror-the-compose-file-docker-compose-yaml-is-invalid-because-contains-uns%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
