docs(faq): out-of-memory issue
parent
b1668492cd
commit
9098619f10
5
faq.md
5
faq.md
|
@ -22,4 +22,7 @@
|
|||
+ Deploy *key* has write access but cannot be used with the HTTPS method, hence, the workaround to clone using SSH.
|
||||
+ Another approach is [personal access token](https://docs.gitlab.com/ee/user/profile/personal_access_tokens.html) which seems HTTPS-compatible.
|
||||
+ Deploy/SSH key is preferred because it can be [restricted](https://docs.gitlab.com/ce/ssh/README.html#per-repository-deploy-keys) to access one repo only, unlike personal access token which has [global](https://docs.gitlab.com/ce/ssh/README.html#global-shared-deploy-keys) access.
|
||||
+ See issue [#18106](https://gitlab.com/gitlab-org/gitlab-ce/issues/18106), [#20567](https://gitlab.com/gitlab-org/gitlab-ce/issues/20567) and [#20845](https://gitlab.com/gitlab-org/gitlab-ce/issues/20845).
|
||||
+ See issue [#18106](https://gitlab.com/gitlab-org/gitlab-ce/issues/18106), [#20567](https://gitlab.com/gitlab-org/gitlab-ce/issues/20567) and [#20845](https://gitlab.com/gitlab-org/gitlab-ce/issues/20845).
|
||||
|
||||
- Script terminated halfway with "grep broken pipe" or "grep killed" error
|
||||
+ This is an out-of-memory (OOM) issue due to large input file. Recommend 3GB+ RAM.
|
||||
|
|
Loading…
Reference in New Issue