mirror of
https://github.com/immich-app/immich.git
synced 2025-01-16 16:56:46 +01:00
docs: update FAQ for Docker (#8418)
* Update FAQ.mdx * Update FAQ.mdx * linting
This commit is contained in:
parent
3682e76dee
commit
700622e521
1 changed files with 24 additions and 2 deletions
|
@ -253,8 +253,19 @@ The initial backup is the most intensive due to the number of jobs running. The
|
||||||
|
|
||||||
### Can I limit the amount of CPU and RAM usage?
|
### Can I limit the amount of CPU and RAM usage?
|
||||||
|
|
||||||
By default, a container has no resource constraints and can use as much of a given resource as the host's kernel scheduler allows.
|
By default, a container has no resource constraints and can use as much of a given resource as the host's kernel scheduler allows. To limit this, you can add the following to the `docker-compose.yml` block of any containers that you want to have limited resources.
|
||||||
You can look at the [original docker docs](https://docs.docker.com/config/containers/resource_constraints/) or use this [guide](https://www.baeldung.com/ops/docker-memory-limit) to learn how to limit this.
|
|
||||||
|
```yaml
|
||||||
|
deploy:
|
||||||
|
resources:
|
||||||
|
limits:
|
||||||
|
# Number of CPU threads
|
||||||
|
cpus: '1.00'
|
||||||
|
# Gigabytes of memory
|
||||||
|
memory: '1G'
|
||||||
|
```
|
||||||
|
|
||||||
|
For more details, you can look at the [original docker docs](https://docs.docker.com/config/containers/resource_constraints/) or use this [guide](https://www.baeldung.com/ops/docker-memory-limit).
|
||||||
|
|
||||||
### How can I boost machine learning speed?
|
### How can I boost machine learning speed?
|
||||||
|
|
||||||
|
@ -296,6 +307,17 @@ You may need to add mount points or docker volumes for the following internal co
|
||||||
|
|
||||||
The non-root user/group needs read/write access to the volume mounts, including `UPLOAD_LOCATION`.
|
The non-root user/group needs read/write access to the volume mounts, including `UPLOAD_LOCATION`.
|
||||||
|
|
||||||
|
For a further hardened system, you can add the following block to every container except for `immich_postgres`.
|
||||||
|
|
||||||
|
```yaml
|
||||||
|
security_opt:
|
||||||
|
# Prevent escalation of privileges after container is started
|
||||||
|
- no-new-privileges:true
|
||||||
|
cap_drop:
|
||||||
|
# Prevent access to raw network traffic
|
||||||
|
- NET_RAW
|
||||||
|
```
|
||||||
|
|
||||||
### How can I **purge** data from Immich?
|
### How can I **purge** data from Immich?
|
||||||
|
|
||||||
Data for Immich comes in two forms:
|
Data for Immich comes in two forms:
|
||||||
|
|
Loading…
Reference in a new issue