toolshed/docs.coopcloud.tech
toolshed/docs.coopcloud.tech
4
1
Fork 19
Code Issues 1 Pull Requests 1 Packages Releases Activity

Add further links
All checks were successful
continuous-integration/drone/push Build is passing
Details

Browse Source
This commit is contained in:
decentral1se 2021-03-11 00:19:18 +01:00
parent 37ff3a1542
commit 0811a1f2f2
No known key found for this signature in database
GPG Key ID: 92DAD76BD9567B8A
1 changed files with 4 additions and 0 deletions
Show Stats 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.)
- 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?
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/).