-
Notifications
You must be signed in to change notification settings - Fork 246
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
Get-BcContainerAppRuntimePackage in Run-ALPipeline #3801
Comments
The generation of a runtime package within Run-AlPipeline should never have been made, since this will only generate a runtime package for a single version of BC. |
Hi Freddy, thanks for your answer. I executed the command on a local maschine and get the following error. It looks like a problem when publishing apps. |
I think apps parameter needs to be an app path or array of app paths - not a folder. |
I tried this with a path to a Appfile: The same error occurs. I think the app file will not copied correctly in container. The same error was already mentioned in the following issue: |
Please provide the full output from your command (not as a screenshot). |
|
Not sure what is wrong, but the command works just fine with a single app without dependencies:
Maybe remove the licensefile - that isn't needed anyway |
I tried now the same appfile on a different maschine wich is running windows server 2019 and older version of docker (Docker Client Version 19.03.5, Docker Server Version 19.03.5) |
Windows 11 has problems with process isolation (which I can see you are running) - that might be the issue.
|
thanks for this info.
|
Hi,
I have allready a problem with debugging when I create runtime packages over the command Run-ALPipeline.
There ist no possibilty to set parameter IncludeSourceInPackageFile.
What can I do, to create debuggable runtime packages over the Run-ALPipeLine command?
In our app.json the parameter allowDebugging and includeSourceInSymbolFile are set to true.
Originally posted by @RalleSP86 in #3160
The text was updated successfully, but these errors were encountered: