-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
[BUG]: Issue with Obsolete DockerCompose Version in Auto-generated File #20129
Comments
@fogwildflower, could you please clarify something for me? Are you experiencing this as a blocking error, or is it just a warning? |
We are also getting this, but on self-hosted/built VMSS Scaleset Agents. It's not a blocking error, but it is reported as an error on the pipeline in red:
The file is definitely being generated by Azure DevOps somehow. We don't create the file and if I SSH into the agent after the pipeline has run, the file doesn't exist. |
Thank you for your response, its a warning messages, showing as error, last night with deployed with this warning, everything is working. |
@fogwildflower how is this issue closed? was there an fix for it deployed? We're still experiencing this in every pipeline |
I'm still experiencing this issue in my pipelines as well |
Basically with this error message app is able to deployed, as I mentioned above its should be a warning message but unfortunately its showing as error. Please Check you application is deploying or not. |
It's deploying, but that's besides the point. The message still shows up as an error on the pipeline which causes confusion for anyone reviewing the pipeline (say, because they are an Approver). The docker) compose file generation performed by Azure DevOps should be fixed |
True |
@TheVexy, @ViggoValfridsson, the PR #20197 changes have been rolled out. |
This is still an issue for me. The pipeline isn't blocked but haven't just updated the DockerCompose task to version 2 (DockerCompose@1) I am still seeing an error output within after execution. `Starting: DockerComposeTask : Docker Compose
|
@satarr could you share your Docker Compose YAML file if possible, or alternatively, provide a minimal example YAML for reproducibility? |
@ivanduplenskikh After creating a mock of the yml I found the section the obsolete version is referencing and it is NOT related to this bug. This is not an issue. Sorry for the interruption. |
New issue checklist
Task name
DockerCompose
Task version
1
Issue Description
Hi,
I'm encountering an issue with the DockerCompose@1 task in Azure DevOps, specifically related to an obsolete version of Docker Compose being used in the auto-generated file. Here's the problem I'm facing:
When using the DockerCompose@1 task to build docker images, I've recently updated Docker Compose on the agents. However, now I'm receiving warnings during execution that indicate an obsolete version in the auto-generated compose file:
##[error]time="2024-07-08T12:11:47Z" level=warning msg="/home/vsts/agents/3.241.0/.docker-compose.1720440594107.yml:
version
is obsolete"It appears that this auto-generated compose file includes the version at the top, but I haven't found an option within the task to disable or update this to a non-obsolete version.
Any insights or guidance on how to address or work around this issue would be greatly appreciated.
Thank you!
Environment type (Please select at least one enviroment where you face this issue)
Azure DevOps Server type
dev.azure.com (formerly visualstudio.com)
Azure DevOps Server Version (if applicable)
No response
Operation system
Ubuntu Latest
Relevant log output
##[error]time="2024-07-08T12:11:47Z" level=warning msg="/home/vsts/agents/3.241.0/.docker-compose.1720440594107.yml: `version` is obsolete"
Full task logs with system.debug enabled
Repro steps
No response
The text was updated successfully, but these errors were encountered: