mirror of
https://github.com/IT4Change/gradido.git
synced 2025-12-13 07:45:54 +00:00
45 lines
1.3 KiB
Markdown
45 lines
1.3 KiB
Markdown
# Docker More Closely
|
|
|
|
## Apple M1 Platform
|
|
|
|
***Attention:** For using Docker commands in Apple M1 environments!*
|
|
|
|
### Enviroment Variable For Apple M1 Platform
|
|
|
|
To set the Docker platform environment variable in your terminal tab, run:
|
|
|
|
```bash
|
|
# set env variable for your shell
|
|
$ export DOCKER_DEFAULT_PLATFORM=linux/amd64
|
|
```
|
|
|
|
### Docker Compose Override File For Apple M1 Platform
|
|
|
|
For Docker compose `up` or `build` commands, you can use our Apple M1 override file that specifies the M1 platform:
|
|
|
|
```bash
|
|
# in main folder
|
|
|
|
# for development
|
|
$ docker compose -f docker-compose.yml -f docker-compose.override.yml -f docker-compose.apple-m1.override.yml up
|
|
|
|
# for production
|
|
$ docker compose -f docker-compose.yml -f docker-compose.apple-m1.override.yml up
|
|
```
|
|
|
|
## Analysing Docker Builds
|
|
|
|
To analyze a Docker build, there is a wonderful tool called [dive](https://github.com/wagoodman/dive). Please sponsor if you're using it!
|
|
|
|
The `dive build` command is exactly the right one to fulfill what we are looking for.
|
|
We can use it just like the `docker build` command and get an analysis afterwards.
|
|
|
|
So, in our main folder, we use it in the following way:
|
|
|
|
```bash
|
|
# in main folder
|
|
$ dive build --target <layer-name> -t "gradido/<app-name>:local-<layer-name>" <app-folder-name-or-dot>/
|
|
```
|
|
|
|
For the specific applications, see our [publish.yml](.github/workflows/publish.yml).
|