Official Docker images for Deno across multiple Linux distributions including Alpine, Debian, Ubuntu, and distroless.
deno_docker is the official collection of Docker images for the Deno runtime, providing pre-built containers for running Deno applications in isolated environments. It solves the problem of setting up Deno across different operating systems by offering ready-to-use images for popular Linux distributions. These images ensure consistent behavior and simplify deployment workflows for Deno-based projects.
Developers and DevOps engineers who use Deno for building applications and need to containerize them for deployment, testing, or development environments. It's particularly useful for teams adopting Docker in their CI/CD pipelines.
Developers choose deno_docker because it offers officially maintained, optimized images that reduce setup time and ensure compatibility with Deno's latest features. The variety of base images allows for customization based on size, security, and performance requirements.
Latest dockerfiles and images for Deno - alpine, centos, debian, ubuntu
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Images are maintained by the Deno team, ensuring timely updates and compatibility with the latest Deno releases, as seen in the regular version tags like 2.7.11.
Supports multiple Linux distributions—Alpine, Debian, Ubuntu, and distroless—allowing developers to choose based on size, security, or stability needs.
Includes a non-root 'deno' user by default to reduce attack surfaces, and provides guidance for secure practices like setting DENO_DIR in cloud environments.
Offers specific advice for Google Cloud Run to avoid caching conflicts, simplifying deployment for serverless setups.
The project is tightly coupled with Docker; for other container systems, users must manually adapt the setup, which isn't documented.
Only covers specific Linux distributions; if a team requires a different base like CentOS or Windows containers, they need to use the binary image and handle integration themselves.
Containerization adds layers and latency compared to native Deno execution, which can slow down development iteration and increase resource usage in some scenarios.