Files
computer-playbook/roles/dsk-docker
kevinveenbirkenbachandClaude Opus 5 ff734fe728 feat(licensing): declare the deployed software's licence per role
The project licence governs this repository's code and says nothing about the application a role installs, which is where a restriction on commercial use usually sits: a deployment cleared to use Infinito.Nexus commercially is still barred from NLLB-200's CC BY-NC weights.

Each invokable role names its licence in meta/<role>/license.yml with the url it was read from. The rights of a named licence live once in meta/licenses.yml, fifteen fields following the taxonomy choosealicense publishes. AND folds to the strictest combination, OR keeps the most favourable whole licence, and the seven contexts are derived from the rights rather than declared, so a heading cannot contradict the matrix under it.

The generated page renders one matrix per context, a lint refuses a role that declares nothing, and a Playwright spec asserts the page against the deployed docs. 21 of 22 deprecated SPDX ids were resolved against the upstream text; EPSON's remains unread because its AUR page blocks automated access.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-10-20 23:35:00 +02:00
..
…
…

Workstation Docker

Description

Installs Docker and Docker Compose, and adds a user to the Docker group for non-root usage on development machines.

Overview

This playbook, dsk-docker, is part of a larger collection housed within the infinito repository. It is specifically tailored for setting up Docker and Docker Compose on personal computers (PCs) used for development purposes. The primary goal is to facilitate a development environment on individual workstations rather than configuring servers for hosting or distributing Docker images.

Features

The main.yml file in the dsk-docker role consists of two primary tasks:

  1. Install Docker: This task uses the community.general.pacman module to install docker and docker-compose on the system. It ensures that these packages are present on the PC.

  2. User Group Configuration: This task adds a specified user (denoted as {{users.client.username}}) to the Docker user group. This is crucial for allowing the specified user to interact with Docker without needing superuser permissions.

Use Case

The playbook is designed for developers who require Docker in their local development environments. It simplifies the process of Docker installation and configuration, making it straightforward for developers to start containerizing their applications without the complexities often encountered in a server or production environment.

Prerequisites

  • Ansible: Ensure that Ansible is installed on your system to run this playbook.
  • Arch Linux-based System: This playbook uses the pacman package manager, indicating it's designed for Arch Linux-based systems.

Running the Playbook

To run this playbook:

  1. Clone the infinito repository.
  2. Navigate to the roles/dsk-docker directory.
  3. Run the playbook using the appropriate Ansible commands, ensuring that you have the necessary privileges.

Important Notes

  • Not for Server Use: This playbook is not designed for server environments. It is optimized for individual development machines.
  • Customization: You may need to customize the playbook, especially the {{users.client.username}} variable, to suit your specific setup.
  • Security Considerations: While adding a user to the Docker group provides ease of use, be aware of the security implications. It grants the user elevated privileges which, if misused, can affect the entire system.

Support & Contribution

For support, suggestions, or contributions, please raise an issue or a pull request in the infinito repository. This project welcomes contributions from the developer community.