53 lines
1.8 KiB
Markdown
53 lines
1.8 KiB
Markdown
|
|
#### debug :
|
|
|
|
- `docker exec -ti <container-name> bash` to run bash inside a running container
|
|
- `docker logs <container_name>` to see the logs on standard output of a container
|
|
- `docker ps` to list the container, and see their names
|
|
|
|
#### todo :
|
|
|
|
- **VOLUMES :** it still not clear the better way to deal with volumes :
|
|
- if i use named bind volumes with :
|
|
```
|
|
services:
|
|
wordpress:
|
|
volumes:
|
|
- wp_plugin:/path/inside/container
|
|
|
|
volumes:
|
|
wp_plugins:
|
|
driver: local
|
|
driver_opts:
|
|
type: none
|
|
o: "bind"
|
|
device: /path/on/local/machine
|
|
```
|
|
- the folder on host has its ownerships changed, because it's recreated by docker
|
|
- so the pbm is that if the plugin folder has no content yet, you need to use sudo to change its owner back to the user
|
|
- instead i can use bind mount like in this answer :
|
|
- https://stackoverflow.com/questions/77949712/docker-compose-ownership-of-named-bind-volume-with-specified-path?noredirect=1#comment137421603_77949712
|
|
```
|
|
- /path/on/local/machine:/path/inside/container
|
|
```
|
|
- but if i do it with mariadb volume, container mariadb cannot work anymore
|
|
- i dont have time to understand why, but certainly it doesn't have the appropriates rights anymore
|
|
- and anyway what is the difference with this :
|
|
- https://docs.docker.com/storage/bind-mounts/
|
|
- https://docs.docker.com/compose/compose-file/compose-file-v3/#volumes
|
|
```
|
|
- type: bind
|
|
source: ./static
|
|
target: /opt/app/static
|
|
```
|
|
- **ERRORS LOG :** it would be better to have a way to see all the error logs from all containers
|
|
maybe with a volume for logs
|
|
- in the meantime, here are the logs :
|
|
- wordpress : /var/www/html/wp-content/
|
|
as precised in the wp-config.php file with DEBUG_LOGS variable,
|
|
that i create in wp_entrypoint.sh
|
|
- mariadb :
|
|
- nginx :
|
|
|
|
|