knoflook/docs.coopcloud.tech
0
0
Fork 0
forked from toolshed/docs.coopcloud.tech
Code Issues Pull Requests Projects Releases Wiki Activity

Add further links

Browse Source
This commit is contained in:
decentral1se
2021-03-11 00:19:18 +01:00
parent 37ff3a1542
commit 0811a1f2f2
1 changed files with 4 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/faq.md
View File

@ -168,6 +168,10 @@ With that all in mind, here are some leading thoughts.
- How do I audit my container security in an on-going process (IDS, OSSEC, Apparmor, etc.) - How do I audit my container security in an on-going process (IDS, OSSEC, Apparmor, etc.)
- Can I run my containers with a [non-root user setup](https://docs.docker.com/engine/security/rootless/)? - Can I run my containers with a [non-root user setup](https://docs.docker.com/engine/security/rootless/)?
And further reading on this topic:
- [Docker security documentation](https://docs.docker.com/engine/security/)
## Why use the Compose specification? ## Why use the Compose specification?
Every application packaged for the Co-op Cloud is described using a file format which uses the [compose specification](https://compose-spec.io/). It is important to note that we do not use the [Docker compose](https://docs.docker.com/compose/) tool itself to deploy apps using this format, instead we rely on [Docker swarm](https://docs.docker.com/engine/swarm/stack-deploy/). Every application packaged for the Co-op Cloud is described using a file format which uses the [compose specification](https://compose-spec.io/). It is important to note that we do not use the [Docker compose](https://docs.docker.com/compose/) tool itself to deploy apps using this format, instead we rely on [Docker swarm](https://docs.docker.com/engine/swarm/stack-deploy/).