centersl/portainer-docs
1
0
Fork 0
mirror of https://github.com/portainer/portainer-docs.git synced 2026-03-27 04:48:31 +07:00
Code Issues Packages Projects Releases Wiki Activity

GITBOOK-52: Add information on orphaned stacks and update FAQ

Browse Source
This commit is contained in:
Hannah Cooper
2025-11-30 19:56:53 +00:00
committed by gitbook-bot
parent d154d1fa66
commit 9fa81d169e
24 changed files with 26 additions and 28 deletions
Download Patch File Download Diff File Expand all files Collapse all files

BIN
.gitbook/assets/Orphaned-stack-associate-FAQ.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 211 KiB

BIN
.gitbook/assets/Show-orphaned-stacks-FAQ (1).png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 133 KiB

BIN
.gitbook/assets/Show-orphaned-stacks-FAQ.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 133 KiB

2
admin/environments/add/docker/edge-async.md
View File

@@ -41,7 +41,7 @@ Select **Docker Standalone** then click **Start Wizard**. Then select the **Edge
| Name | Enter a name for your environment. |
| Portainer API server URL | Enter the URL and port of your Portainer Server instance as it will be seen from your Edge environment. If using a FQDN, ensure that DNS is properly configured to provide this. |
<figure><img src="../../../../.gitbook/assets/2.18-environments-add-docker-edge-async-name (1).png" alt=""><figcaption></figcaption></figure>
<figure><img src="/broken/files/9cqG768bKKshymxybpuv" alt=""><figcaption></figcaption></figure>
As an optional step you can expand the **More settings** section and adjust the **Ping**, **Snapshot** and **Command** intervals for the environment - this defines how often this Edge Agent will check in with the Portainer Server for status updates, snapshot updates and to see if there are new pending commands to run, respectively. The default for each is once a minute, but the defaults can be adjusted in the [Edge Compute settings](../../../settings/edge.md#async-check-in-intervals).&#x20;

2
admin/environments/add/podman/edge-async.md
View File

@@ -41,7 +41,7 @@ Select **Podman** then click **Start Wizard**. Then select the **Edge Agent Asyn
| Name | Enter a name for your environment. |
| Portainer API server URL | Enter the URL and port of your Portainer Server instance as it will be seen from your Edge environment. If using a FQDN, ensure that DNS is properly configured to provide this. |
<figure><img src="../../../../.gitbook/assets/2.18-environments-add-docker-edge-async-name (1).png" alt=""><figcaption></figcaption></figure>
<figure><img src="/broken/files/9cqG768bKKshymxybpuv" alt=""><figcaption></figcaption></figure>
As an optional step you can expand the **More settings** section and adjust the **Ping**, **Snapshot** and **Command** intervals for the environment - this defines how often this Edge Agent will check in with the Portainer Server for status updates, snapshot updates and to see if there are new pending commands to run, respectively. The default for each is once a minute, but the defaults can be adjusted in the [Edge Compute settings](../../../settings/edge.md#async-check-in-intervals).&#x20;

3
faqs/contributing/how-do-i-log-a-support-request.md
View File

@@ -3,8 +3,7 @@
Only Portainer Business (BE) customers with a Professional or Enterprise subscription can log tickets directly with Portainer. For all other users, we recommend our [community support resources](https://www.portainer.io/get-support-for-portainer?hsLang=en).
\
**How to log a support request:**\
**How to log a support request:**<br>
* Go to the [Get Support](https://www.portainer.io/get-support-for-portainer?hsLang=en) page on the Portainer website.
* After reviewing the existing resources to see if your question has already been answered, scroll down to the **Get Business Edition Support** section and complete the form.

6
faqs/getting-started/how-does-portainer-respond-to-cves.md
View File

@@ -4,8 +4,7 @@ description: In this article we'll talk about CVEs and how we respond to them at
# How does Portainer respond to CVEs?
The crucial points are:\
The crucial points are:<br>
* CVEs are reports of vulnerabilities in software.
* CVEs are given a score (between 0.0 and 10.0) based on a number of criteria.
@@ -16,8 +15,7 @@ The crucial points are:\
* Many reported CVEs in Portainer are actually in third-party binaries, which can slow down fix timeframes.
* Some CVEs are submitted without enough information, and we can (and have) mark these as disputed.
Below we'll go into more detail on each of the above points.\
Below we'll go into more detail on each of the above points.<br>
#### What is a CVE?

2
faqs/installing/how-do-i-install-portainer.md
View File

@@ -1,4 +1,4 @@
# How do I install Portainer?
Portainer installation depends on a number of things. This includes the installation environment (Docker Standalone, Docker Swarm, Kubernetes) and the platform that the environment runs on (Linux, Windows, Serverless).\
New to Portainer? Our [getting started guide](broken-reference) will walk you through the installation process. For our more experienced users, we recommend reading the guide or taking a look at our more comprehensive [installation instructions](../../start/install/).
New to Portainer? Our [getting started guide](/broken/pages/-MgDXUT1Y2VDzEaLxVhV) will walk you through the installation process. For our more experienced users, we recommend reading the guide or taking a look at our more comprehensive [installation instructions](../../start/install/).

3
faqs/installing/portainer-isnt-starting-on-my-windows-server-help.md
View File

@@ -2,8 +2,7 @@
When running Portainer Server or the Portainer Agent on a Windows server, you may be presented with an error similar to the following:
`failure in a Windows system call: The system cannot find the file specified.`\
`failure in a Windows system call: The system cannot find the file specified.`<br>
In some instances we have seen antimalware software (in particular, Trend Micro Deep Security) silently removing the Portainer and Agent executables from container images when they are pulled. As a result, when the container attempts to start it is missing the executable it needs, and returns the above error.\
In this instance, you can restore the removed executables to the image from within your antimalware software (for Trend Micro Deep Security, this documentation may help). We would also advise adding exceptions for portainer.exe and agent.exe in your antimalware configuration to prevent this in the future.

2
faqs/licensing/my-portainer-extensions-license-has-expired.-what-can-i-do.md
View File

@@ -22,4 +22,4 @@ If you have more than 3 nodes, please complete our [additional pricing request f
We have [complete guides](../../start/upgrade/tobe/) on how to upgrade from 1.24.x to Portainer Business Edition for your platform.
For more on why you should transition to Portainer Business Edition, we have a [blog post](https://www.portainer.io/blog/why-transition-to-portainer-business-from-portainer-extensions?hsLang=en) that goes into detail as to the benefits of doing so.\
For more on why you should transition to Portainer Business Edition, we have a [blog post](https://www.portainer.io/blog/why-transition-to-portainer-business-from-portainer-extensions?hsLang=en) that goes into detail as to the benefits of doing so.<br>

2
faqs/licensing/what-is-a-node-for-licensing-purposes.md
View File

@@ -26,7 +26,7 @@ In this scenario, Portainer is running in three places (one Server and two Agent
Now, for Docker Swarm let's imagine a setup with one manager node (manager01) and two worker nodes (swarm01 and swarm02):
<figure><img src="../../.gitbook/assets/image (3).png" alt=""><figcaption></figcaption></figure>
<figure><img src="/broken/files/aSrLWsspksJWMJAwUndl" alt=""><figcaption></figcaption></figure>
Portainer Server is running on the manager node, and the agent is running on all three nodes across the swarm. Therefore, this would also require a 3 node license.

2
faqs/licensing/what-is-the-pricing-for-business-edition.md
View File

@@ -98,4 +98,4 @@ Optional extra services:
| **Portainer Professional Services (Services)** | Advanced services for consulting, implementation, configuration and support (hourly basis) |
| **Managed Platform Services** | Portainer's managed platform services team will accelerate your containerization journey. |
\
<br>

2
faqs/troubleshooting/access-and-authentication/client-sent-an-http-request-to-an-https-server.md
View File

@@ -32,4 +32,4 @@ Alternatively if you have HTTP access enabled you can access via HTTP on port 90
http://my.portainer.url:9000/
```
\
<br>

2
faqs/troubleshooting/access-and-authentication/i-enabled-force-https-only-and-now-im-locked-out-of-portainer.-how-do-i-get-back-in.md
View File

@@ -43,4 +43,4 @@ If you are unable to adjust the run command to include the command line option,
You should now be able to log in to Portainer using HTTP.
\
<br>

3
faqs/troubleshooting/access-and-authentication/unable-to-login-via-ldap-in-portainer.md
View File

@@ -42,7 +42,6 @@ Use a local Portainer admin account to access the Portainer web interface.
{% step %}
**Save Changes**
Save the updated settings and ensure that the connection is stable.\
Save the updated settings and ensure that the connection is stable.<br>
{% endstep %}
{% endstepper %}

3
faqs/troubleshooting/logs-errors-and-debugging/why-is-my-console-closing-after-a-certain-time.md
View File

@@ -16,8 +16,7 @@ proxy_read_timeout 3600;
&#x20;\
**Nginx Proxy Manager:**
Edit the proxy host that you need to change and add `proxy_read_timeout 3600;` as below.\
Edit the proxy host that you need to change and add `proxy_read_timeout 3600;` as below.<br>
<figure><img src="../../../.gitbook/assets/image (16).png" alt=""><figcaption></figcaption></figure>

4
faqs/troubleshooting/stacks-deployments-and-updates/how-do-i-recover-orphaned-stacks-from-a-previously-deleted-environment.md
View File

@@ -6,11 +6,11 @@ Stacks from an environment that has been deleted will be labelled as orphaned st
1. Within the environment that you want to associate your orphaned stacks with, click **Stacks** in the left hand menu. At the Stacks list, click on the three dots in the top right corner and select **Show all orphaned stacks**. Your stack list will then update to include any orphaned stacks.
<div align="left"><figure><img src="../../../.gitbook/assets/orphaned stacks selection.png" alt=""><figcaption></figcaption></figure></div>
<div align="left"><figure><img src="../../../.gitbook/assets/Show-orphaned-stacks-FAQ (1).png" alt=""><figcaption></figcaption></figure></div>
2. Click into the stack that you want to recover, and select **Associate.**
<figure><img src="../../../.gitbook/assets/associate.png" alt=""><figcaption></figcaption></figure>
<figure><img src="../../../.gitbook/assets/Orphaned-stack-associate-FAQ.png" alt=""><figcaption></figcaption></figure>
Your stack will now appear in your stack list with total control. Repeat this process for each stack you want to reassociate.

2
user/account-settings.md
View File

@@ -59,7 +59,7 @@ To add a new credential, click the **Add git credential** button and fill out th
| Username | Enter the username, if relevant. |
| Personal Access Token | Enter the personal access token. |
<figure><img src="../.gitbook/assets/2.33-account-git-creds-new.png" alt=""><figcaption></figcaption></figure>
<figure><img src="/broken/files/nJsNFlKSiOkomPKUgwMN" alt=""><figcaption></figcaption></figure>
Once you've entered the relevant details, click **Save git credential** to save the entry.

2
user/aci/containers/README.md
View File

@@ -22,4 +22,4 @@ From this page you can add a new container or remove existing containers:
\
<br>

2
user/docker/images/export.md
View File

@@ -14,4 +14,4 @@ When the warning message appears, click **Continue**.
<figure><img src="../../../.gitbook/assets/2.15-images-export-confirm.png" alt=""><figcaption></figcaption></figure>
When the image has downloaded, a success message will appear, and your browser should automatically download the resulting tar file.\
When the image has downloaded, a success message will appear, and your browser should automatically download the resulting tar file.<br>

2
user/docker/images/pull.md
View File

@@ -12,7 +12,7 @@ This method lets you pull images from Docker Hub or from another registry that y
From the menu select **Images**. Select the registry to use then enter the name of the image. On a multi-node environment, select the node to deploy to.
<figure><img src="../../../.gitbook/assets/2.15-docker_images_pull_images (1).png" alt=""><figcaption></figcaption></figure>
<figure><img src="/broken/files/0gsoANgVX6ylmlLvlYkk" alt=""><figcaption></figcaption></figure>
When you're ready, click **Pull the image**.

2
user/docker/services/configure.md
View File

@@ -14,7 +14,7 @@ In this section you can:
* View the [service logs](logs.md).
* Update, [roll back](rollback.md) or delete the service.
<figure><img src="../../../.gitbook/assets/2.15-docker_services_service_details (1).png" alt=""><figcaption></figcaption></figure>
<figure><img src="/broken/files/3LlEyQXwKwwHMUYOkLzN" alt=""><figcaption></figcaption></figure>
## Container specification configuration options

4
user/docker/stacks/README.md
View File

@@ -4,6 +4,10 @@ A stack is a collection of services, usually related to one application or usage
<figure><img src="../../../.gitbook/assets/2.20-stacks-list.png" alt=""><figcaption></figcaption></figure>
Within the Stack list, you’ll see all stacks that have been previously created in the selected environment. If an environment is deleted, any stacks that belonged to it become orphaned. To display any orphaned stacks, click the three dots in the top right corner and select **Show all orphaned stacks**, [the stack will need to be re-associated](../../../faqs/troubleshooting/stacks-deployments-and-updates/how-do-i-recover-orphaned-stacks-from-a-previously-deleted-environment.md) to be fully recovered.
<figure><img src="../../../.gitbook/assets/Show-orphaned-stacks-FAQ.png" alt=""><figcaption></figcaption></figure>
When the [new image indicator](../host/setup.md#other) feature is enabled, the **Images up to date** column indicates whether the local images in the stack are up to date, with a green tick indicating they are up to date and an orange cross indicating that there is a newer version of an image available at the remote registry. A grey hyphen indicates Portainer was unable to determine whether there is an update available for the images.
You can click the **Reload image indicators** button to recheck the images for your stacks for updates, or to recheck a single stack's images you can click the image indicator icon for that stack.

2
user/docker/stacks/edit.md
View File

@@ -78,7 +78,7 @@ You can also toggle the stack [webhook](webhooks.md) and retrieve the webhook UR
You can choose to **Prune services** if you have made changes that remove some services from the stack.
<figure><img src="../../../.gitbook/assets/2.20-stacks-edit-swarm-prune.png" alt=""><figcaption></figcaption></figure>
<figure><img src="/broken/files/5cu2Q9GNn6Gzxrb7wVP1" alt=""><figcaption></figcaption></figure>
When you have finished making changes, click **Update the stack**.