mirrors/dozzle
1
0
Fork 0
mirror of https://github.com/amir20/dozzle.git synced 2025-12-21 13:23:07 +01:00
Code Issues Projects Releases Wiki Activity

docs: Fixes for previous commit of Podman host not found errors documentation (#3408)

Browse Source
This commit is contained in:
Rhea Alleen
2024-11-19 19:31:27 +01:00
committed by GitHub
parent 50855a8700
commit 95de5a8504
3 changed files with 8 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
README.md
View File

@@ -97,9 +97,9 @@ Once you have the podman remote socket you can run Dozzle on podman.
podman run --volume=/run/user/1000/podman/podman.sock:/var/run/docker.sock -d -p 8080:8080 amir20/dozzle:latest
```
Additionally you have to create a fake engine-id to prevent ```host not found``` errors. Podman doesn´t generate an engine-id like Docker by itself due to its daemonless architecture.
Additionally you have to create a fake engine-id to prevent ```host not found``` errors. Podman doesn't generate an engine-id like Docker by itself due to its daemonless architecture.
Under ```/var/lib/docker``` create a file named ```engine-id```, on a system with Podman you will have to creater the folder path as well. Inside the file place a UUID, for instance using ```uuidgen > engine-id```. After that the file should have an identifier that looks like this: ```b9f1d7fc-b459-4b6e-9f7a-e3d1cd2e14a9```.
Under ```/var/lib/docker``` create a file named ```engine-id```. On a system with Podman you will have to create the folder path as well. Inside the file place the UUID, for instance using ```uuidgen > engine-id```. After that the file should have an identifier that looks like this: ```b9f1d7fc-b459-4b6e-9f7a-e3d1cd2e14a9```.
For more details check [Podman Infos](docs/guide/podman.md) or the [FAQ](docs/guide/faq.md#i-am-seeing-host-not-found-error-in-the-logs-how-do-i-fix-it)

4
docs/guide/faq.md
View File

@@ -104,9 +104,9 @@ To resolve the error take following steps:
The engine-id file should now have an UUID inside.
An example setup for Ansible can be found in [Podman](podman.md)
An example setup for Ansible can be found in [Podman Infos](podman.md)
It might be neccessary to clean up your existing dozzle deployment under Podman, stop the container and remove the associated data (container/volumes). After that you can redeploy the Dozzle container and your logs should now show up.
It might be necessary to clean up your existing Dozzle deployment under Podman, stop the container and remove the associated data (container/volumes). After that you can redeploy the Dozzle container and your logs should now show up.
## Why am I only seeing running containers? How do I see stopped containers?

8
docs/guide/podman.md
View File

@@ -7,7 +7,7 @@ title: Podman
This should be mainly a Podman only error: Using Podman doesn't create an engine-id like Docker.
If you are using Docker check if the ```engine-id``` file exists with correct permissions in ```/var/lib/docker``` and has the UUID inside.
It might be neccessary to clean up your existing dozzle deployment under Podman, stop the container and remove the associated data (container/volumes). After you created the engine-id you can redeploy the Dozzle container and your logs should now show up.
It might be necessary to clean up your existing Dozzle deployment under Podman, stop the container and remove the associated data (container/volumes). After you created the engine-id you can redeploy the Dozzle container and your logs should now show up.
## Create UUID
@@ -15,7 +15,7 @@ Options for generating UUIDs
### uuidgen
:warning: Adjust folder/file permissions if necessary. There isn't an critial info but depending on your existing setup you might want to take additional steps
:warning: Adjust folder/file permissions if necessary. There isn't any critial info but depending on your existing setup you might want to take additional steps
1. Install uuidgen
2. Create the folders: ```mkdir -p /var/lib/docker```
@@ -24,9 +24,9 @@ Options for generating UUIDs
### Ansible
:warning: Depending on your setup you might have to take adjustments for file/folder permissions. The following task snippets would run as the become_user of the playbook running these tasks.
:warning: Depending on your setup you might have to take adjustments for file/folder permissions. The following task snippets would run as the become_user/remote_user of the playbook running these tasks.
If you wish to adjust the user have to set individual become/become_user parameters for the task.
If you wish to adjust the user you have to set individual become/become_user parameters for these tasks.
```
- name: Create /var/lib/docker