Custom Apt Dpkg Non Repo Install

What the dpkg external package installer does

This Automox Worklet™ installs software packages on Linux endpoints using external.deb files that are not available in standard apt repositories. The Worklet downloads the package from a specified URL, installs it using apt-get with the local file path, and removes the temporary file after successful installation.

The Worklet supports apt/dpkg-based Linux distributions including Ubuntu, Debian, and their derivatives. It uses wget to retrieve the package file and apt-get to perform the installation with quiet output to reduce console noise.

This approach allows you to deploy software from custom package sources such as vendor-hosted repositories, internal mirrors, or third-party hosting without adding permanent repository configurations to your endpoints.

Why deploy packages from external sources

Many organizations use software packages that are not available in default Linux repositories. Examples include proprietary applications, internal tools, and vendor-specific software. Manual installation across hundreds of endpoints is time-consuming and error-prone.

By automating external package installation through Automox, you eliminate manual deployment work and maintain consistent package versions across your endpoint fleet. This is particularly valuable when deploying security tools, monitoring agents, or line-of-business applications that require regular updates.

Using external URLs also provides flexibility for organizations with internal package mirrors or those that cannot modify system repository configurations due to security policies.

How external package installation works

1. Evaluation phase: Always returns a non-zero exit code, indicating that the Worklet should proceed to remediation. This allows the Worklet to perform the installation regardless of current state.

2. Remediation phase: Uses wget to download the.deb package from the specified URL to the /tmp directory, then runs apt-get install with the local file path. If installation succeeds, the temporary file is removed. If either download or installation fails, appropriate error messages are logged.

External package installation requirements

• Linux endpoint running an apt/dpkg-based distribution such as Ubuntu, Debian, Linux Mint, or Pop!_OS

• wget command-line utility installed and available in the system PATH

• apt-get and dpkg package management tools installed

• Root or sudo privileges to execute apt-get install commands

• Network connectivity to reach the external package URL

• Sufficient disk space in the /tmp directory to temporarily store the.deb file

• Customize the INSTALLER_URL variable in the remediation script with the URL of the.deb package to install

Expected state after package installation

After the Worklet completes successfully, the specified .deb package will be installed on the endpoint. The package name, version, and files will be tracked by the dpkg database on the system, making it available for standard apt package management operations such as updates and uninstallation.

The Worklet removes the temporary.deb file from /tmp after installation, verifying no leftover installation files remain. You can verify successful installation by running commands such as dpkg -l to list installed packages or by checking the application or service is available on the endpoint.

How to validate custom apt dpkg non repo install changes

1. Run this Worklet on a pilot Linux endpoint and review evaluation output for custom apt dpkg non repo install.

2. Confirm Automox activity logs show successful completion and exit code 0.

3. Verify endpoint state using checks aligned to evaluation script logic, such as exit.

4. Validate remediation effects from script operations such as rm, else, then rerun evaluation for compliance.