Package Linux application dependencies for the VM's actual repository access

Source facts

Microsoft warns that individual Linux package downloads usually omit dependencies. A VM Application must include those dependencies or let the target’s package manager obtain them from reachable repositories; restricted-internet targets need the dependencies packaged. The documented Ubuntu workflow also cautions against explicitly removing every bundled dependency because another installed application may share it. Package and removal design therefore need separate checks. Microsoft Learn.

Applicability

Identify the target distribution, release, architecture, existing package state, and repository access. Treat the source’s example package lists as illustrations rather than an inventory for every current image. Establish which dependencies must travel with the package and which approved repositories will remain available during deployment.

DSE recommendation

Build and test the dependency bundle against the target distribution and its permitted repository paths. Keep a manifest of package versions and provenance with the application version. Design removal around the target package manager’s dependency handling and have the application owner identify shared components that must remain. Avoid solving a missing package by opening unrestricted outbound access without a separate network decision.

Verification

Install the bundle on a representative clean test VM under the intended connectivity restrictions. Check the application’s actual workflow and retain missing-dependency or repository errors. Then rehearse removal while another representative application remains installed, verifying that its shared dependencies still function. Record both installation and removal outcomes so a successful connected build does not substitute for evidence from the restricted target environment.

Official references

Microsoft Learn: Create packages for VM applications. Source reviewed September 9, 2026.