DevOps/truecharts
2
0
Fork 0
Code Issues Pull Requests Actions 29 Packages Projects Releases 1 Wiki Activity

Minor spelling and grammar fixes (#35817)

Browse Source 
**Description**
<!--
Please include a summary of the change and which issue is fixed. Please
also include relevant motivation and context. List any dependencies that
are required for this change.
-->
⚒️ Fixes  # <!--(issue)-->

**⚙️ Type of change**

- [ ] ⚙️ Feature/App addition
- [ ] 🪛 Bugfix
- [ ] ⚠️ Breaking change (fix or feature that would cause existing
functionality to not work as expected)
- [ ] 🔃 Refactor of current code
- [ ] 📜 Documentation Changes

**🧪 How Has This Been Tested?**
<!--
Please describe the tests that you ran to verify your changes. Provide
instructions so we can reproduce. Please also list any relevant details
for your test configuration
-->

**📃 Notes:**
<!-- Please enter any other relevant information here -->

**✔️ Checklist:**

- [ ] ⚖️ My code follows the style guidelines of this project
- [ ] 👀 I have performed a self-review of my own code
- [ ] #️⃣ I have commented my code, particularly in hard-to-understand
areas
- [ ] 📄 I have made changes to the documentation
- [ ] 🧪 I have added tests to this description that prove my fix is
effective or that my feature works
- [ ] ⬆️ I increased versions for any altered app according to semantic
versioning
- [ ] I made sure the title starts with `feat(chart-name):`,
`fix(chart-name):`, `chore(chart-name):`, `docs(chart-name):` or
`fix(docs):`

**➕ App addition**

If this PR is an app addition please make sure you have done the
following.

- [ ] 🖼️ I have added an icon in the Chart's root directory called
`icon.png`

---

_Please don't blindly check all the boxes. Read them and only check
those that apply.
Those checkboxes are there for the reviewer to see what is this all
about and
the status of this PR with a quick glance._

Signed-off-by: bitpushr <91350598+bitpushr@users.noreply.github.com>
Signed-off-by: Alfred Göppel <43101280+alfi0812@users.noreply.github.com>
Co-authored-by: Alfred Göppel <43101280+alfi0812@users.noreply.github.com>
This commit is contained in:
bitpushr
2025-06-03 09:23:27 +02:00
committed by GitHub
co-authored by Alfred Göppel
parent e23fdd2d1c
commit dfc7c1fc54
1 changed files with 13 additions and 16 deletions
Download Patch File Download Diff File Expand all files Collapse all files
website/src/content/docs/guides/talos/docker.md
+13 -16
View File
@@ -4,26 +4,26 @@ title: Talos as a Docker-Compose App
:::caution[Disclaimer]
This guide is not covered by the Support Policy and some features wont work when running Talos as a dockerfile.
This guide is not covered by the Support Policy and some features won't work when running Talos as a dockerfile.
:::
Talos can be run as a docker container. This has a couple of downsides like:
Talos can now be run as a docker container. This has a couple of downsides such as:
- No system-extensions
- No TalosCTL reset -> restart the containers and/or wipe container storage instead
- Dependance on host-kernel -> host kernel might not be optimised for talos
- Dependance on host-kernel -> host kernel might not be optimised for Talos
- No MetalLB -> use ServiceLB or node port instead
- No TalosCTL Upgrade -> update the container instead
- Nvidia GPU Assignment
- Warning spam in container logs that it cant alter bpf related stuff
- Warning spam in container logs that it can't alter bpf-related stuff
- CEPH and such can hijack drives -> Be careful!
## Setup Instructions
### Docker Compose YAML
Following you will find a `compose.yml` on how to run Talos as a docker container.
Below you will find a `compose.yml` on how to run Talos as a docker container.
```yaml
services:
@@ -92,10 +92,10 @@ networks:
### Clustertool
#### talconfig
#### Talconfig
This modification for your talconfig, should allow for automatic selection of the container NIC.
This is needed for each node defined
This modification for your talconfig should allow for automatic selection of the container NIC.
This is needed for each node defined.
@@ -110,7 +110,7 @@ nodes:
#### Machineconfig
Running Talos inside a dockerfile requires some modifications to talos machine config:
Running Talos inside a dockerfile requires some modifications to Talos' machine config:
```yaml
@@ -138,18 +138,15 @@ After Clustertool bootstrap, be sure to delete/comment-out:
### ClusterTool compatibility
The able has previously been tested with "normal" useage of `talosctl apply`, on machineconfigs created, and manually altered, using `clustertool genconfig`.
Its not been validated for clustertool bootstrapping as of yet
The tool has previously been tested with "normal" usage of `talosctl apply` on machineconfigs created and manually altered using `clustertool genconfig`.
It's not been validated for clustertool bootstrapping as yet.
### Intel GPU support
We assume that doing the volume-forwards to the container like normal for adding intel GPUs to containers, would work fine.
But we've not tested this yet
We assume that doing the volume-forwards to the container like normal for adding intel GPUs to containers works fine, but we've not tested this yet.
### OpenEBS ZFS-PV
We assume that the included /dev/zfs forward is going to be enough to even setup OpenEBS ZFS-PV with access to the pool.
But we've not officially tested this.
We assume that the included /dev/zfs forward is going to be enough to even setup OpenEBS ZFS-PV with access to the pool, but we've not officially tested this.