xsrv VS compose-spec

Yes, OpenLDAP installed from this ansible role

It's dead easy to use TCP/SSL instead of UDP to forward logs. Example rsyslog config

I use rsyslog for that since it's the default in Debian. Configuring forwarding is very simple, a single file in /etc/rsyslog.d/forwarding.conf [1]. Note that this setup uses TLS to encrypt messages so you need to create the relevant certificates (I use self-signed certs). Unencrypted TCP or UDP is simpler, but less secure.

preseed.cfg contains a few basic options needed to setup the OS [1]

I do this with https://github.com/nodiscc/xsrv/tree/master/roles/openldap + https://github.com/nodiscc/xsrv/tree/master/roles/samba. It's just a standalone samba server + LDAP auth for users, no DC or anything like that, so I'm not sure this is what you're looking for.

This ansible role (check the tasks/ directory) gives a good breakdown of what is needed to setup a basic LDAP server and authentication service

I use samba in standalone mode with or without LDAP auth https://github.com/nodiscc/xsrv/tree/master/roles/samba

Specification: https://compose-spec.io

https://github.com/compose-spec/compose-spec/blob/master/spe...

There are a number of incorrect statements in this post.

1) One should neither be using the "latest" nor just the "version" tag as the version can still vary depending on when it is pulled.

Instead, one should use a combination of version + hash, say alpine:3.18.2@sha256:82d1e9d7ed48a7523bdebc18cf6290bdb97b82302a8a9c27d4fe885949ea94d1 for reproducibility reasons. This provides for human readable versions as well as the specific hash.

2) Next, afaik, Compose has removed the need for version tags. All of the compose.yml files that I now use do not specify versions.

See https://github.com/compose-spec/compose-spec/blob/master/04-...

Docker Compose v2 specifications provide a useful Secrets feature which may also be used for standalone Compose Application Stacks and not just in Docker Swarm mode. With Docker Secrets the environment variables that contain credentials for other subsystems are mounted into the Telegraf Container as files. These secret files are read through the Docker Secret Store plugin and passed to the respective plugins in a relatively safe manner. By using the Docker Secret Store Plugin, one can also avoid credentials that were previously visible via environment variables, to be now hidden behind runtime secret files within the container. Standard Method with Environment Variables As an example, it is possible to pass the credentials to a plugin via the environment variable placeholder in a telegraf configuration file where the credentials for a plugin exist in a .env file (e.g. MQTT input Plugin)

also the docker-compose.yml file is very picky about what you have in it and where. Please read this so you know how to format it https://github.com/compose-spec/compose-spec/blob/master/spec.md

As part my quadlet helper tool, podlet, I'm adding functionality to convert compose files into k8s yaml to use with quadlet as an alternative to creating a bunch of separate quadlet files, which I've also added functionality for. So I would like to be able to transform the options on compose volumes into k8s yaml. For example, using the volume.podman.io/driver annotation to change the volume driver for a specific volume if possible.

If you find this helpful feature, please leave your feedback and suggestions here.

The compose spec will give what you need. https://github.com/compose-spec/compose-spec/blob/master/spec.md

Indeed, as per the compose-spec a lot of what was version specific is going away

Hello everyone, I just made a tool to visualize compose files, and all the parsing rules follow the [compose-spec](https://github.com/compose-spec/compose-spec/blob/master/spec.md). I hope this tool will help you :D