microsoft / microsoft/Oryx

oryx cannot build some reference like "xmlsec" automatically

Open
#2,471 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C#
Stars
881
Forks
195
Avg merge
20h 13m
Merged PRs (30d)
13

Description

Bug Report
  • 2024/07/04 I decide to feedback this problem. It's not the first time i meet this bug, but it starts to affect my work recently, it appeared nearly 2 years age.

  • I enperience this problem in Azure web apps.

  • We used the web app with python stack and windows os to deploy our websites. But 2 years ago, the type of web app we used had been retired. So we wanted to find another way to deploy our projects.

  • At that time, we only had one type web app with linux os to choose(we don't want to use docker untill we have no choice, because our customer think docker deployment will bring safety issues), so we tried to create a new web app with python stack and linux os to deploy.

  • However, when the webapp tried to pull deployment files from git repos, we found that deployment failed. After discussed with Azure support team, we found that oryx couldn't install some references like "xmlsec", so we needed to install this reference. but when we pull the files again , the reference(xmlsec) we installed in the web app had been cleaned from the web app, this mad us give up using linux os web app.

  • Today,we find that out web site is scaned with a safety issue: tornado 6.1 has a known vulnerability; So we have to resolve this safety issue. To fix it, we need to change our deployment, to use high version webapp.

  • As we are in China, we just have linux os web app to choose. So if we can't deploy out project in this way, we have to use docker, it will bring a lot unknown problems.

  • Can we fix this bug? Or can you provide a list of unsupport references ?

  • To reproduce this issue, I think we just need to deploy a project with the reference xmlsec.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source file or test is named. Start by reproducing an Azure Linux web app deployment for a Python project that depends on xmlsec, then trace how Oryx installs and cleans deployment dependencies. Done means the deployment behavior is corrected or the unsupported-reference behavior is clearly identified and documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, python
Domain
build-system, cloud, devops
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.