kudu | engine behind git/hg deployments | Azure library
kandi X-RAY | kudu Summary
kandi X-RAY | kudu Summary
Kudu is the engine behind git deployments in Azure App Service. It can also run outside of Azure.
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of kudu
kudu Key Features
kudu Examples and Code Snippets
Community Discussions
Trending Discussions on kudu
QUESTION
I'm trying to deploy my locally fine running function to Azure
- VS Code Version: 1.65.2
- Azure Tools v0.2.1
- Azure Functions v1.6.1
My requirements.txt
ANSWER
Answered 2022-Apr-07 at 13:42This is linked to and open Github issue with Microsoft Oryx.
Hey folks, apologies for the breaking changes that this issue has caused for your applications.
Oryx has pre-installed Python SDKs on the build images; if the SDK that your application is targeting is not a part of this set, Oryx will fallback to dynamic installation, which attempts to pull a Python SDK that meets your application's requirements from our storage account, where we backup a variety of Python SDKs.
In this case, it appears that the Python 3.9.12 SDK was published to our storage account yesterday around 3:10 PM PST (10:10 PM UTC), and applications targeting Python 3.9 are now pulling down this 3.9.12 SDK rather than the previously published 3.9.7 SDK.
I'm optimistic that we should have this resolved in the next couple of hours, but in the meantime, as folks have mentioned above, if you are able to downgrade your application to using Python 3.8, please consider doing so. Alternatively, if your build/deployment method allows you to snap to a specific patch version of Python, please consider targeting Python 3.9.7, which was the previous 3.9.* version that can be pulled down during dynamic installation.
Again, apologies for the issues that this has caused you all.
Temporarily try rolling your Python version back down to Python 3.8.
QUESTION
I have delegated access to Azure resources in a third-party tenant using Lighthouse, and this works fine via the portal; users receive the roles expected (typically Contributor).
However, they are unable to access Kudu (at webappname.scm.azurewebsites.net), receiving an error;
Selected user account does not exist in tenant 'Tenant Name' and cannot access the application 'abfa0a7c-a6b6-4736-8310-5855508787cd' in that tenant. The account needs to be added as an external user in the tenant first. Please use a different account.
If the same user account is added as a guest to the third-party tenant and given the same role, they can access Kudu as expected.
It's clear that Kudu is expecting/demanding an account in the same tenant as the application, but Azure Lighthouse delegated permissions is all about not having to do that.
Is there something I'm missing, or another role that needs granting?
...ANSWER
Answered 2022-Mar-30 at 06:21@PhilD, Thanks for the detailed description of the scenario. I have also posted this on your Q&A thread.
Currently, Kudu is not compatible with Lighthouse-delegated permissions.
Our product engineering team is working on it; however, we do not have an exact ETA to share. We’re expecting it to be available in a few months. Please note that this timeline is just an estimate and is subject to change, depending on a myriad of factors.
I have relayed the feedback internally to our product engineering team and it’s being tracked.
-On a side note, as mentioned in this Kudu wiki : “Only those with Contributor / Owner access (to be exact, with microsoft.web/sites/publish/action or, for slot, microsoft.web/sites/slots/publish/action) can access to Kudu (SCM).”
Much appreciate your valuable feedback on this. Thanks for your patience!
QUESTION
I updated my Asp.net core Blazor WebAssembly app to .net 6. Everything is fine, but the deploy from github actions doesn't work and throws this error:
...ANSWER
Answered 2021-Nov-15 at 05:26On Linux, it's important that any bash deployment scripts that get run have Unix line endings (LF) and not Windows line endings (CRLF).
Kuduscript will generate scripts with platform-appropriate line endings, but if those scripts are modified, or if you provide your own custom deployment scripts, it's important to make sure that your editor doesn't change the line endings.
If something seems off with your deployment script, you can always use the Kudu console to delete the contents of /home/site/deployments/tools.
This is the directory where Kudu caches kuduscript-generated deployment scripts. On the next deployment, the script will be regenerated.
The error you're currently seeing is a Kudu issue with running node/npm for deployments.
The easiest and fastest resolution for what you are currently seeing is to specify engines.node in your package.json.
Error: EISDIR: illegal operation on a directory, open '/home/site/wwwroot/wwwroot/Identity/lib/bootstrap/LICENSE'
EISDIR stands for "Error, Is Directory". This means that NPM is trying to do something to a file but it is a directory. In your case, NPM is trying to "read" a file which is a directory. Since the operation cannot be done the error is thrown.
Three things to make sure here
- Make sure the file exists. If it does not, you need to create it. (If NPM depends on any specific information in the file, you will need to have that information there).
- Make sure it is in fact a file and not a directory.
- It has the right permissions. You can change the file to have all permissions with "sudo chmod 777 FILE_NAME".
Note: You are giving Read, Write and Execute permissions to every one on that file.
QUESTION
I have a Blazor WebAssembly (Core Hosted) solution for testing purpose. I test 2 different scenario:
1st one: publishing the server side on Azure and the client side inside a storage account.
2nd one: publishing everything on Azure
FYI my solution is composed of 3 projects
- Client
- Server
- Shared (Razor Class Library) <-- with some Blazor components + css + js + ...
The 1st scenario
For publishing the server side: right click on the Server project then choose Publish, then choose Azure (fill in settings,...) then start the publishing process.
For publishing the client side: right click on the Client project then choose Publish, then choose Folder, then start the publishing process. Next, I used the Microsoft Azure Storage Explorer app to upload files (located in \bin\Release\net5.0\browser-wasm\publish\wwwroot\ ) inside the storage account.
I clearly see that:
- my static assets (css, js, ...) are inside \wwwroot\ _content\
- my dll files (Prolog.Client.dll, Prolog.Shared.dll among many others) are inside \wwwroot\ _framework
And everything is working as expected.
The 2nd scenario
For publishing everything on Azure, simply right click on the Server project then choose Publish, then choose Azure (fill in settings,...) then start the publishing process.
Everything is working as expected.
Thanks to the kudu website (https:// myappxxx. scm .azurewebsites.net/) I can browse files on my server. I easily located my dll files inside the wwwroot folder on the server (Prolog.Client.dll, Prolog.Server.dll, Prolog.Shared.dll among many others).
But what is obscure to me is to know where are physically located my static assets ? Where are my css and js files ?
Can I use the Kudu website to browse through folders to find them ?
For example, below, my javascript file named main.js. I tried to use the Kudu website to locate it on my server where it has been published without luck. I don't find any _content folder nor Prolog.Shared folder.
UPDATE
Thanks to Mister Magoo : I tried the "App Service Editor (Preview)" under the "Development Tools" section of the Azure Portal for my App Service. From there I was able to browse through all my files, including my static assets. It was pretty similar to the Kudu console... except that in my Kudu console some files and folders were missing. I noticed a warning message in my Kudu console:
So I added this key in my Local Storage and bingo! All my missing files were suddenly visible. Problem solved.
...ANSWER
Answered 2021-Nov-25 at 09:26Have you tried the "App Service Editor (Preview)" under the "Development Tools" section of the Azure Portal for your App Service? I can see the _content files there for mine.
QUESTION
I have a .net core 3.1 mvc project, and published to azure web app. Then in kudu -> home/site/wwwroot, I created a html file, like below:
But when I want to visit the html page via azure web app like this "https://xxx.azurewebsites.net/test111.html", it has 404 error:
Are there any way to fix this, from code or azure portal?
...ANSWER
Answered 2021-Oct-28 at 07:49Looks like you have an ASP.NET Core app? Have you enabled serving of static files, re:
https://docs.microsoft.com/en-us/aspnet/core/fundamentals/static-files?view=aspnetcore-5.0
QUESTION
We have two Azure functions, let's call them A and B, that we deploy using Azure Devops. Looking at the deployment logs, first the right package is deployed followed by a deploy where the contents of Function App A are deployed to Function app B. How this happens is a mystery.
The strange things is, looking at the logs and what is inside Kudu, they don't match up. For example, the latest deploy logs will say this:
...ANSWER
Answered 2021-Sep-20 at 06:53Apparantly this is happening because both Functions are hosted on the same App Service plan and thus using the same Azure File Share. See this thread https://github.com/projectkudu/kudu/issues/3333.
QUESTION
I'm deploying an HTTP Trigger function to Azure Function but when I'm trying to access entries in process.env
it returns undefined
. It does work in the local emulator but does not when deployed on Azure.
I've tested it with a very simple HTTP function.
...ANSWER
Answered 2021-Sep-11 at 19:21After try fixing things for almost 5 hours. I figured out it was a missing configuration in the Function App.
FUNCTIONS_WORKER_RUNTIME
needs to be set to node
(this was done automatically when deploying the resource directly from Visual Studio Code Extension)
If you are using Terraform
QUESTION
We have a build/release pipeline that is finally working correctly, but the developer asked that we exclude the stage config files (Web.Dev.config, Web.Test.config, Web.Prod.config) as well as the artifact archive itself from the site/wwwroot.
As you can see, everytime we deployed, these zip files have been getting stored in the site root as well. They arent harmful but it doesnt look good
This is the Release App Service Web Deploy YAML
...ANSWER
Answered 2021-Jul-02 at 16:34You can add an additional arguments line to the yml that will tell it to skip certain files. It will look something like this:
QUESTION
ANSWER
Answered 2021-Jul-04 at 17:11You can use the parameter SCM_BUILD_ARGS
. Here is the documentation.
e.g. via a .deployment
file:
QUESTION
I've got several webjobs that I deploy using an Azure DevOps pipeline. After the .NET 5 migration I have these errors in Kudu
This happened after .net 5 migration but I don't really think it is connected to it. The app service configuration is set to NET5.
I already try these actions:
- Manually delete all jobs in kudu and redeploy them
- Deploy the webjobs in another app service
- Obviously (ironically) in the local environment it works
The fact that they won't work in another app service means the problem is in the devOps pipeline, but I didn't change it. I mean, it builds in net5 right now, that's all.
Could someone know about this type of error? I never encountered something like this in kudu and It's difficult to even search for a solution.
Thanks in advance.
...ANSWER
Answered 2021-Apr-14 at 01:18You can add extension on portal or in scm
site. After installed ASP.NET Core 5.0 (x86 and x64) Runtime
, your issue will be solved.
1. On portal.
2. On scm
site.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install kudu
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page