Skip to content

Commit

Permalink
+ portainer
Browse files Browse the repository at this point in the history
  • Loading branch information
klaxalk committed Dec 3, 2024
1 parent 9ab3b89 commit 8da1110
Show file tree
Hide file tree
Showing 8 changed files with 537 additions and 14 deletions.
7 changes: 0 additions & 7 deletions docs/10-prerequisities/30-docker/60-airgapped-machines.md

This file was deleted.

7 changes: 7 additions & 0 deletions docs/10-prerequisities/30-docker/60-offline-machines.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
---
title: Offline machines
pagination_label: Working with offline machines
description: How to work with offline machines
---

# Offline machines with Docker
7 changes: 0 additions & 7 deletions docs/10-prerequisities/32-portainer.md

This file was deleted.

126 changes: 126 additions & 0 deletions docs/10-prerequisities/32-portainer/01-starting.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,126 @@
---
title: Starting Portainer
pagination_label: Starting Portainer
description: Starting Portainer
---

# Starting Portainer

Portainer can be started using a simple compose session.
By default, the containers will respawn when the computer restarts.

## Portainer Agent

The Portainer Agent is responsible for communicating with the local docker daemon.

<details>
<summary>Compose file</summary>

```yaml
services:

portainer_agent:

image: portainer/agent:2.21.0

ports:
- 9001:9001

volumes:
- /var/run/docker.sock:/var/run/docker.sock
- /var/lib/docker/volumes:/var/lib/docker/volumes
- /:/host

restart: always
```
</details>
## Portainer Server
The Portainer Server is what creates the Web UI.
A single server can be connected to more than one **agent**.
<details>
<summary>Compose file</summary>
```yaml
volumes:

portainer_data:

services:

portainer:

image: portainer/portainer-ce:2.21.0

ports:
- 8000:8000
- 9000:9000
- 9443:9443

volumes:
- /var/run/docker.sock:/var/run/docker.sock
- portainer_data:/data

restart: always

command: --http-enabled
```
</details>
## Both the Agent and the Server on a single machine
In case of a single robot, we might run both on a single machine.
In that case, a single session for both will suffice.
<details>
<summary>Compose file</summary>
```yaml
volumes:

portainer_data:

services:

portainer_agent:

image: portainer/agent:2.21.2

network_mode: host

ports:
- 9001:9001

volumes:
- /var/run/docker.sock:/var/run/docker.sock
- /var/lib/docker/volumes:/var/lib/docker/volumes
- /:/host

restart: always

portainer:

image: portainer/portainer-ce:2.21.2

network_mode: host

ports:
- 8000:8000
- 9000:9000
- 9443:9443

volumes:
- /var/run/docker.sock:/var/run/docker.sock
- portainer_data:/data

restart: always

command: --http-enabled

```

</details>
13 changes: 13 additions & 0 deletions docs/10-prerequisities/32-portainer/10-connecting-to.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,13 @@
---
title: Connecting to Portainer
pagination_label: Connecting to Portainer
description: Connecting to Portainer
---

# Connecting to portainer

1. Open your web browser
2. Determine the hostname of the machine that run Portainer (e.g., `localhost`, or `uav1`)
3. Open the url [https://localhost:9443](https://localhost:9443) (substitude your hostname)

![](./fig/portainer_login.png)
Loading

0 comments on commit 8da1110

Please sign in to comment.