Note: This error originates from a subprocess, and is likely not a problem with pip.ĮRROR: Could not build wheels for pycairo, which is required to install pyproject.toml-based projects To the PKG_CONFIG_PATH environment variableĬommand '' returned non-zero exit status 1. Perhaps you should add the directory containing `cairo.pc' Package cairo was not found in the pkg-config search path. The parts of the log detailing what failed reads as follows:īuilding wheels for collected packages: pycairoīuilding wheel for pycairo (pyproject.toml): startedīuilding wheel for pycairo (pyproject.toml): finished with status 'error'īuilding wheel for pycairo (pyproject.toml) did not run successfully.Ĭreating build/lib.linux-x86_64-cpython-38Ĭreating build/lib.linux-x86_64-cpython-38/cairoĬopying cairo/ init.py -> build/lib.linux-x86_64-cpython-38/cairoĬopying cairo/ init.pyi -> build/lib.linux-x86_64-cpython-38/cairoĬopying cairo/py.typed -> build/lib.linux-x86_64-cpython-38/cairo.Oryx takes over and performs a second build job on Azure's side and fails.After the steps complete, the files are sent to Azure in a second Deploy job.Navigate to the Actions tab on GitHub and you will notice the build steps complete successfully on GitHub.Connect it with GitHub with Continuous Integration turned on so that changes in this repository will invoke the new deploy workflow Azure places into the repo.Create a new Azure Web Apps instance for Linux-Python 3.8 in Canada Central or US East.Create a GitHub repo and create a new file app.py with the following Flask Python code:.Was hoping to get some advice on how to remediate the issue.
Please quote this in all correspondence.I've run into deployment failures for my Flask app to Azure Web Apps recently. Failed to execute goal com.spotify:docker-maven-plugin:0.4.5:build (server) on project web-service: Exception caught: : .rs.ProcessingException: .HttpHostConnectException: Connect to localhost:2375 failed: Connection refused -> Ĭould it be that port 2375 needs to be forwarded to localhost? Informationĭocker logs are being collected into /tmp/. I think some tools depends on DOCKER_HOST to be set Actual behavior It might be a problem with the plugin implementation, (and I have filed a bug). I would like to have the maven plugin to be able to do it’s job.
0 kommentar(er)
