initial import

Author: simonwalz

.dockerignore

@@ -0,0 +1 @@
+output/

.editorconfig

@@ -0,0 +1,27 @@
+# Editor configuration, see https://editorconfig.org
+root = true
+
+[*]
+charset = utf-8
+indent_style = space
+indent_size = 2
+insert_final_newline = true
+trim_trailing_whitespace = true
+
+[*.ts]
+quote_type = single
+
+[*.md]
+max_line_length = off
+trim_trailing_whitespace = false
+
+[*.cs,*.py]
+indent_style = space
+indent_size = 4
+
+
+[*.hbs,*.{diff,md}]
+insert_final_newline = false
+
+[*.sh]
+end_of_line = lf

.gitignore

@@ -0,0 +1,4 @@
+.*.un~
+.*.swp
+old/
+output/

.pipeline-test.sh

@@ -0,0 +1,13 @@
+#!/bin/bash
+
+status=0
+
+while IFS= read -r -d '' file; do
+    echo "Running: $file"
+    if ! bash "$file"; then
+        echo "❌ Failed: $file"
+        status=1
+    fi
+done < <(find . -type f -name "*.test.sh" -print0)
+
+exit "${status}"

.pipeline.json

@@ -0,0 +1,27 @@
+{
+	"images": [
+		{
+			"subname": "updater",
+			"context": "updater",
+			"pretest": [
+				{
+					"script": "apk add bash; ./.pipeline-test.sh"
+				}
+			]
+		},
+		{
+			"subname": "system",
+			"context": "system"
+		},
+		{
+			"subname": "system-lxc",
+			"context": "system",
+			"dockerfile": "Dockerfile_lxc"
+		},
+		{
+			"subname": "image",
+			"context": "",
+			"dockerfile": "image/Dockerfile"
+		}
+	]
+}

CODE_OF_CONDUCT.md

@@ -0,0 +1,129 @@
+
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, caste, color, religion, or sexual
+identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+- Demonstrating empathy and kindness toward other people
+- Being respectful of differing opinions, viewpoints, and experiences
+- Giving and gracefully accepting constructive feedback
+- Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+- Focusing on what is best not just for us as individuals, but for the overall
+  community
+
+Examples of unacceptable behavior include:
+
+- The use of sexualized language or imagery, and sexual attention or advances of
+  any kind
+- Trolling, insulting or derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or email address,
+  without their explicit permission
+- Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official email address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+Walz.
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of
+actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or permanent
+ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the
+community.
+
+## Attribution
+
+This Code of Conduct is adapted from the
+[Contributor Covenant](https://www.contributor-covenant.org/), version 2.1,
+available at
+<https://www.contributor-covenant.org/version/2/1/code_of_conduct/>.
+
+Community Impact Guidelines were inspired by
+[Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/inclusion).
+
+For answers to common questions about this code of conduct, see the FAQ at
+<https://www.contributor-covenant.org/faq/>. Translations are available at
+<https://www.contributor-covenant.org/translations/>.
+

CONTRIBUTING.md

@@ -0,0 +1,65 @@
+# Contributing to CuOS (Container Update OS)
+
+We welcome contributions from the community!
+
+- All contributors are expected to follow our [Code of Conduct](CODE_OF_CONDUCT.md).
+- All contributions must comply with the [Developer Certificate of Origin (DCO)](DCO.txt). This means adding a Signed-off-by line to your commits.
+
+---
+
+## 🚀 Why Contribute?
+
+CuOS is built on the idea that your OS should be managed just like your containers. By contributing, you're helping create a system where:
+
+- All tools and configurations are defined in a container image.
+- Updates are automatic and rollback-safe.
+- The OS is reproducible, scalable, and fleet-ready.
+- Developers can reuse their container knowledge to manage entire systems.
+
+---
+
+## 🧰 Getting Started
+
+### 1. Fork the Repository
+
+Click the **Fork** button on GitHub to create your own copy of the project.
+
+### 2. Clone Your Fork
+
+```bash
+git clone https://github.com/your-username/cuos.git
+cd cuos
+```
+
+## 🐛 Reporting Issues
+
+If you encounter a bug or have a feature request:
+
+  1 Check the issue tracker to see if it’s already reported.
+  2 If not, open a new issue with:
+    * A clear title and description
+    * Steps to reproduce (if applicable)
+    * Expected vs. actual behavior
+    * Logs or screenshots if helpful
+
+## ✨ Submitting Pull Requests
+
+  1 Create a new branch:
+    `git checkout -b feature/your-feature-name`
+
+  2 Make your changes and commit them:
+    `git commit -m "feat: your feature description"`
+
+Note: You can signed-off your commits by `git commit -s ...`.
+See [Developer Certificate of Origin (DCO)](DCO.txt).
+
+## 🤝 Community Guidelines
+
+We value respectful, inclusive, and constructive collaboration. Please:
+
+  * Be kind and respectful in all interactions.
+  * Use clear and concise language.
+  * Provide helpful feedback and be open to receiving it.
+  * Follow the [Code of Conduct](CODE_OF_CONDUCT.md).
+
+Thank you for helping make CuOS better!

DCO.txt

@@ -0,0 +1,36 @@
+Developer Certificate of Origin
+Version 1.1
+
+Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
+
+Everyone is permitted to copy and distribute verbatim copies of this
+license document, but changing it is not allowed.
+
+
+Developer's Certificate of Origin 1.1
+
+By making a contribution to this project, I certify that:
+
+(a) The contribution was created in whole or in part by me and I
+    have the right to submit it under the open source license
+    indicated in the file; or
+
+(b) The contribution is based upon previous work that, to the best
+    of my knowledge, is covered under an appropriate open source
+    license and I have the right under that license to submit that
+    work with modifications, whether created in whole or in part
+    by me, under the same open source license (unless I am
+    permitted to submit under a different license), as indicated
+    in the file; or
+
+(c) The contribution was provided directly to me by some other
+    person who certified (a), (b) or (c) and I have not modified
+    it.
+
+(d) I understand and agree that this project and the contribution
+    are public and that a record of the contribution (including all
+    personal information I submit with it, including my sign-off) is
+    maintained indefinitely and may be redistributed consistent with
+    this project or the open source license(s) involved.
+
+Source: https://developercertificate.org/

DISCLAIMER.md

@@ -0,0 +1,7 @@
+# Disclaimer
+
+This software is provided "as is", without any express or implied warranties of any kind. Use of this software is at your own risk. Liability for damages resulting from the use of this software is excluded to the extent permitted by law. This exclusion does not apply in cases of intent or gross negligence.
+
+The software is provided free of charge. There is no entitlement to maintenance, support, or further development.
+
+This disclaimer is intended to comply with German legal requirements, including § 309 No. 7 of the German Civil Code (BGB).

LICENSE.txt

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025 Simon Walz
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.