| Pitfall | Symptom | Solution | |---------|---------|----------| | Version drift | "Module not found" | Use lockfiles and freeze versions | | Incomplete downloads | Checksum error | Always validate checksums | | Permission denied | Cannot write to /usr/lib | Download to user-writable directories or use sudo judiciously | | Network flakiness | Broken pipe / timeout | Add retry logic: curl --retry 3 --retry-delay 2 | | Missing transitive deps | Runtime import errors | Use recursive downloaders ( pip download --no-deps vs default) |
set -euo pipefail
curl --proto '=https' --tlsv1.2 -sSf https://secure-site.com/dep.tar.gz
FROM node:18 WORKDIR /app COPY package.json package-lock.json ./ RUN npm ci --prefer-offline --no-audit --progress=false COPY . .
Let's build a practical example. Imagine you have a Python project with dependencies listed in requirements.txt and a custom binary from GitHub. Here's a shell script that performs a complete "shell dep download":
If you are working in the oil and gas industry, "Shell DEP download" refers to the process of accessing . These documents are the primary technical standards used by Shell to ensure safety, reliability, and efficiency across their global assets.
local deps=( "https://example.com/tool.tar.gz|tool.tar.gz|expected_sha256_here" )