Share via

The given path's format is not supported.

Hammed Ejilola 0 Reputation points
2024-05-15T14:53:53.38+00:00

Whenever I install some node js package (aes-everywhere, or some other hashing algorithm packages) and I want to deploy from the viscose I used to get this error

15:50:08 geotopuptest: Zip package size: 30.4 MB

15:50:09 geotopuptest: Fetching changes.

15:50:09 geotopuptest: Cleaning up temp folders from previous zip deployments and extracting pushed zip file C:\local\Temp\zipdeploy\ddq2cs3y.zip (29.04 MB) to C:\local\Temp\zipdeploy\extracted

15:50:10 geotopuptest: The given path's format is not supported.

15:50:18 geotopuptest: Deployment failed.

but when I uninstall the package it will successfully deploy from viscose

Microsoft Deployment Toolkit
Microsoft Deployment Toolkit
A collection of Microsoft tools and documentation for automating desktop and server deployment. Previously known as Microsoft Solution Accelerator for Business Desktop Deployment (BDD).
842 questions
Microsoft Configuration Manager Deployment
Microsoft Configuration Manager Deployment
Microsoft Configuration Manager: An integrated solution for for managing large groups of personal computers and servers.Deployment: The process of delivering, assembling, and maintaining a particular version of a software system at a site.
920 questions
Azure App Service
Azure App Service
Azure App Service is a service used to create and deploy scalable, mission-critical web apps.
7,070 questions

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. ajkuma 23,181 Reputation points Microsoft Employee
    2024-05-20T15:02:38.57+00:00

    @Hammed Ejilola , Based on my understanding of your issue description, you are experiencing this issue when you install certain node.js packages. it could be due to package in your application which has a dependency on a Linux Shared Library which is missing in the Docker Image.

    You may to add the App Setting SCM_DO_BUILD_DURING_DEPLOYMENT to true and then check.

    Just to highlight, Node packages may rely on Shared Libraries (.so files) that are expected to exist on the current distribution. In this case, since App Service Linux runs in Docker Containers, the distribution and the OS this is built off of would be expected to have these .so files (if needed).

    You may try these approaches:

    1. You may add or modify Custom Startup Script - Checkout this article Azure App Service Linux - Custom Startup Script for Nodejs & Python - on how to implement this. It’s important to note that each .so may require various Linux-based dependencies to be fully installed**.** Check the .so file in question to see what other Linux dependencies may be required for it.

    1. If you haven't done, leverage Custom Docker Image -Nodejs on App Service Linux and why to avoid installing packages in startup scripts, and see if it helps.

    Kindly let us know, I'll follow-up with you further.

    0 comments