Skip to content

Commit

Permalink
Fix Docker build
Browse files Browse the repository at this point in the history
  • Loading branch information
arixmkii committed Sep 1, 2024
1 parent 15e160b commit 99d7ac8
Show file tree
Hide file tree
Showing 2 changed files with 23 additions and 3 deletions.
4 changes: 1 addition & 3 deletions .github/workflows/prepare-docker-release.yml
Original file line number Diff line number Diff line change
Expand Up @@ -55,10 +55,8 @@ jobs:
- name: "📦 Pack Docker"
run: |
mkdir -p qcw
ls docker-cli-release/build
ls docker-compose-release/bin/build
cp docker-cli-release/build/docker-windows-amd64.exe qcw/docker.exe
cp bin/build/docker-compose.exe qcw/docker-compose.exe
cp docker-compose-release/bin/build/docker-compose.exe qcw/docker-compose.exe
cd qcw
find . -type f \( ! -iname "*.checksums" \) -exec sha256sum -b {} \; > sha.checksums
find . -type f \( ! -iname "*.checksums" \) -exec sha512sum -b {} \; >> sha.checksums
Expand Down
22 changes: 22 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -162,6 +162,28 @@ size. If VM is configured correctly and the HW requirements for nested vitrualiz
Podman machine should be the same as on bare metal (the performance is expected to be worse to some extent, because
it runs inside a VM).

### With `docker-compose`

If one has access to `Docker Desktop` it is possible to use binaries distributed by the software to connect them to
Podman. Alternatively it is possible to download pre-built binaries of the CLI and compose plugin from releases page.

After downloading and unpacking binaries one should make the tools discoverable inside `%PATH%`. To make `docker`
recognize the plugin it is recommended to put it into a well-known location like `%USERPROFILE%\.docker\cli-plugins`.
This step is not needed if `Docker Desktop` is used as this configures everythign on your behalf.

Using `podman compose`, when `docker-compose` is discoverable:
```bat
podman compose up --wait
```

Using `docker compose` one needs to provide DOCKER_HOST value with named pipe from
`podman machine inspect --format {{.ConnectionInfo.PodmanPipe.Path}}` converted to URL compatible address:
`\\.\pipe\podman-machine-default` would become `npipe:////./pipe/podman-machine-default`
```bat
set DOCKER_HOST=npipe:////./pipe/podman-machine-default
docker compose up --wait
```

## How to use Lima

TBD
Expand Down

0 comments on commit 99d7ac8

Please sign in to comment.