From 0d9bff6c6a034d3dec7a90c7931316e6855caa29 Mon Sep 17 00:00:00 2001 From: burakberkkeskin Date: Mon, 28 Oct 2024 20:27:08 +0300 Subject: [PATCH 1/3] updated faq for compose parallelism Signed-off-by: burakberkkeskin --- docs/self-hosted-appcircle/faq.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/self-hosted-appcircle/faq.md b/docs/self-hosted-appcircle/faq.md index 41f50ee67..9ca493421 100644 --- a/docs/self-hosted-appcircle/faq.md +++ b/docs/self-hosted-appcircle/faq.md @@ -40,9 +40,11 @@ If you need to use a proxy on the Appcircle server, you should configure proxy s ### We are facing "manifest not found" error when we run the `up` command. -If you are using the Nexus registry and are facing a "manifest not found" error, this is an expected case to occur. Nexus proxy has a known bug while pulling multiple container images. You should pull images one by one as a workaround. +This error often occurs if the images weren’t updated using the `upgrade` command before running the `up` command. [Container image registries](/self-hosted-appcircle/configure-server/external-image-registry.md) can sometimes struggle with simultaneous requests to pull multiple images, leading to issues like "manifest not found." -To pull images one by one, you can see the [Pulling Image One By One](./configure-server/external-image-registry#pulling-images-one-by-one) document. Then you can pull images one by one with this script. So you won't face "manifest not found" error any more. +To address this, the `upgrade` command on the Appcircle server limits the number of pulled images to `5` by default, which helps avoid overloading the container image registry. Make sure to follow the [Upgrade Images](/self-hosted-appcircle/update.md#4-update-images) section carefully to prevent this issue. + +If that didn't work for you, you can try to pull images one by one as a workaround. To pull images one by one, you can see the [Pulling Image One By One](./configure-server/external-image-registry#pulling-images-one-by-one) document. Then you can pull images one by one with this script. So you won't face "manifest not found" error any more. ### Where should we download the zip package while we are updating? From 78a203653d8358e893819f59e7da7f4cce5d0e77 Mon Sep 17 00:00:00 2001 From: burakberkkeskin Date: Mon, 28 Oct 2024 20:28:52 +0300 Subject: [PATCH 2/3] added directory structure Signed-off-by: burakberkkeskin --- docs/self-hosted-appcircle/faq.md | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/docs/self-hosted-appcircle/faq.md b/docs/self-hosted-appcircle/faq.md index 9ca493421..d74d351d1 100644 --- a/docs/self-hosted-appcircle/faq.md +++ b/docs/self-hosted-appcircle/faq.md @@ -48,7 +48,14 @@ If that didn't work for you, you can try to pull images one by one as a workarou ### Where should we download the zip package while we are updating? -Download the zip package of the appcircle server and extract it to the same folder as the already existing Appcircle server folder. Your data and configuration will be saved while updating. +Download the zip package of the appcircle server and extract it to the same folder as the already existing Appcircle server folder. Your data and configuration will be saved while updating. The directory structure should be similar to: + +```bash +. +|-- appcircle-server +|-- appcircle-server-linux-x64-3.22.1-abcd.zip +`-- cred.json +``` ### How do I change Docker or Podman's data location? From b18b5b4cd472078866fda890275716fbdc6a2a2b Mon Sep 17 00:00:00 2001 From: burakberkkeskin Date: Mon, 28 Oct 2024 20:34:19 +0300 Subject: [PATCH 3/3] added how to configure steps --- docs/self-hosted-appcircle/faq.md | 45 ++++++++++++++++++++++++++++++- 1 file changed, 44 insertions(+), 1 deletion(-) diff --git a/docs/self-hosted-appcircle/faq.md b/docs/self-hosted-appcircle/faq.md index d74d351d1..5d0f44f3c 100644 --- a/docs/self-hosted-appcircle/faq.md +++ b/docs/self-hosted-appcircle/faq.md @@ -42,7 +42,50 @@ If you need to use a proxy on the Appcircle server, you should configure proxy s This error often occurs if the images weren’t updated using the `upgrade` command before running the `up` command. [Container image registries](/self-hosted-appcircle/configure-server/external-image-registry.md) can sometimes struggle with simultaneous requests to pull multiple images, leading to issues like "manifest not found." -To address this, the `upgrade` command on the Appcircle server limits the number of pulled images to `5` by default, which helps avoid overloading the container image registry. Make sure to follow the [Upgrade Images](/self-hosted-appcircle/update.md#4-update-images) section carefully to prevent this issue. +To address this, the `upgrade` command on the Appcircle server limits the number of pulled images to `5` by default, which helps avoid overloading the container image registry. Make sure to follow the [Upgrade Images](/self-hosted-appcircle/update.md#4-update-images) section carefully to prevent this issue. You can configure the default parallelism limit from `5` to anything you need with the `global.yaml` of your project: + +- Go to the `appcircle-server` directory. + +```bash +cd appcircle-server +``` + +:::info + +The `spacetech` in the example codes below are example project name. + +Please find your own project name and replace `spacetech` with your project name. + +To see projects, you can check the `projects` directory. + +```bash +ls -l ./projects +``` + +::: + +- Edit the `global.yaml` file of your project and configure the parallelism limit as your needs. + +```bash +vi ./projects/spacetech/global.yaml +``` + +:::caution +If the `container` key already exist in the `global.yaml`, you should just update or add the missing `parallelLimit` key. +::: + +```yaml +container: + parallelLimit: 10 +``` + +- Apply configuration changes. + +```bash +./ac-self-hosted.sh -n "spacetech" export +``` + +Now the `upgrade` command of the Appcircle server will try to pull `10` images at once. If that didn't work for you, you can try to pull images one by one as a workaround. To pull images one by one, you can see the [Pulling Image One By One](./configure-server/external-image-registry#pulling-images-one-by-one) document. Then you can pull images one by one with this script. So you won't face "manifest not found" error any more.