# Dockerfiles

> various Dockerfiles

- Price: free, open source
- Warranty: none; built with AI assistance and provided as is
- Built with: Roff
- Author: Kshitiz Wagle (https://kshitizwagle.com.np)
- Source: https://github.com/kshitizwagle/Dockerfiles
- Page: https://projects.kshitizwagle.com.np/dockerfiles
- Last updated: 2025-12-08

## FAQ

### Is Dockerfiles free?

Yes. Dockerfiles is free to use and open source. The full source code is on GitHub at https://github.com/kshitizwagle/Dockerfiles.

### How do I get Dockerfiles?

Get the source from https://github.com/kshitizwagle/Dockerfiles; the README there covers installation and usage.

### Is there a warranty or support for Dockerfiles?

No. Dockerfiles was built with AI assistance and is provided as is, without warranty. Kshitiz Wagle is not liable for damage or loss. Use it at your own risk.

### Who makes Dockerfiles?

Dockerfiles is built and maintained by Kshitiz Wagle, a software engineer in Lalitpur, Nepal. Portfolio: https://kshitizwagle.com.np.

## README

This repository stores Dockerfiles grouped by language, version, and optional
additions. The goal is to keep reusable and well-organized Docker build
definitions in one place. Each folder represents a technology or base image, and
nested folders reflect version-specific or feature-specific setups.

## Structure

```txt
dockerfiles/
│
└── python/
    └── 3.12/
        └── ghostscript-10.05.1/
            ├── Dockerfile
            └── readme.md
```

## Folder Overview

### python/

Contains Python-based images.

### 3.12/

Holds Dockerfiles that extend the Python 3.12 slim Bookworm image.

### ghostscript-10.05.1/

This folder contains a Python 3.12 based Dockerfile that compiles and installs
Ghostscript 10.05.1 from source. The Dockerfile also installs system
dependencies required for building Ghostscript.

Use this folder when you need a Python 3.12 environment with Ghostscript
included.

## Contribution Guidelines

- Use folders to group images by language or purpose.
- Use versioned folders to avoid conflicts between releases.
- Add a `readme.md` in every folder describing what is inside.
- Keep Dockerfiles concise and focused on a single purpose.
- Follow the same structure when adding new folders.