docker-compose: command not found

[liemlylac]

Hi, this really nice repo for running action in locally.
But I have a problem when running docker-compose in action.

This is output

$ act -j test
[build/test] 🚀  Start image=node:12.6-buster-slim
[build/test]   🐳  docker run image=node:12.6-buster-slim entrypoint=["/usr/bin/tail" "-f" "/dev/null"] cmd=[]
[build/test]   🐳  docker cp src=C:\Users\Liem\docker\wordpress-docker-compose/. dst=/github/workspace
[build/test] ⭐  Run actions/checkout@v2
[build/test]   ✅  Success - actions/checkout@v2
[build/test] ⭐  Run Build service s
[build/test]   | /github/workflow/1: line 2: docker-compose: command not found
[build/test]   ❌  Failure - Build service s
Error: exit with `FAILURE`: 127

This is my workflow config

name: build
on: 
  push:
    branches:
      - master
jobs:
  test:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v2
      - name: Build service s
        run: docker-compose up -d
      - name: List container
        run: docker-compose ps
      - name: Test Wordpress container
        run: docker run --rm --network container:wordpress-docker-compose_wordpress_1 appropriate/curl --retry 3 --retry-connrefused http://localhost:8080/
      - name: Test PhpMyAdmin container
        run: docker run --rm --network container:wordpress-docker-compose_phpmyadmin_1 appropriate/curl --retry 3 --retry-connrefused http://localhost:8888/

This is my docker-compose.yml file

version: '3.7'

services:
  wordpress:
    image: wordpress:latest
    depends_on:
      - wordpress_db
    ports:
      - "8080:80"
#    volumes:
#     - type: bind
#       source: ./wp-content
#       target: /var/www/html/wp-content
    restart: always
    environment:
      WORDPRESS_DB_HOST: wordpress_db:3306
      WORDPRESS_DB_USER: wordpress
      WORDPRESS_DB_PASSWORD: secret
      WORDPRESS_DB_NAME: wordpress

  wordpress_db:
    image: mysql:5.7
    volumes:
      - db_data:/var/lib/mysql
    restart: always
    environment:
      MYSQL_ROOT_PASSWORD: secret
      MYSQL_DATABASE: wordpress
      MYSQL_USER: wordpress
      MYSQL_PASSWORD: secret

  phpmyadmin:
    image: phpmyadmin/phpmyadmin
    depends_on:
      - wordpress_db
    restart: always
    ports:
      - "8888:80"
    environment:
      PMA_HOST: wordpress_db
      MYSQL_ROOT_PASSWORDL: secret
    networks:
      - back

networks:
  back:
volumes:
  db_data: {}

My PC:

• Windows 10. version 1909
• Docker version 19.03.5, build 633a0ea

[cplee]

Related to #107

See https://github.com/nektos/act#runners.

You can customize the image used for the runs-on. I've created an image that is a match to GitHub runners, but its like 15GB!

[cplee]

Closing this as a duplicate of #107

[kenorb]

Related post: https://github.com/orgs/community/discussions/134407

[swuecho]

I create a image with docker and docker-compose.

docker pull echowuhao/act_base:latest

I think it is enough for those who use docker and docker-compose to run tests.

if not, easy to adjust based on the Dockerfile.

https://github.com/swuecho/act_base

[lucasres]

When i run with your image i have this erro

Error: Error response from daemon: pull access denied for echowuhao/act_base, repository does not exist or may require 'docker login': denied: requested access to the resource is denied

[jadhavmanoj]

same here. Any suggestion.

Error: Error response from daemon: pull access denied for echowuhao/act_base, repository does not exist or may require 'docker login': denied: requested access to the resource is denied

[lucasres]

The image is private :(

I tried the image nektos/act-environments-ubuntu:18.04. Docker and docker-composer work well but my container dont mount volume inside

[LucasCtrl]

I rebuild and republish the new image from @swuecho

docker pull lucasctrl/act_base:latest

https://github.com/lucasctrl/act_base

[hotlib]

I rebuild and republish the new image from @swuecho

docker pull lucasctrl/act_base:latest

https://github.com/lucasctrl/act_base

I get the following error:

Error response from daemon: pull access denied for lucasctrl/act_base, repository does not exist or may require 'docker login': denied: requested access to the resource is denied

[LucasCtrl]

Did you tried to be logged in before doing

docker pull lucasalt/act_base:latest

by using

docker login -u USERNAME -p PASSWORD

with your docker hub credentials?

[hotlib]

Did you tried to be logged in before doing

docker pull lucasalt/act_base:latest

by using

docker login -u USERNAME -p PASSWORD

with your docker hub credentials?

no, I thought I could download it without login - I somehow found another link to your image and that I could download without login (don’t remember the URL though) and it works great

[swuecho]

I did not know how I end up delete the image. thanks @LucasCtrl to set it up.

[visini]

Using --platform ubuntu-latest=lucasalt/act_base:latest instead of --platform ubuntu-latest=lucasalt/act_base worked for me without docker login. Many thanks!

[hata6502]

https://docs.docker.jp/compose/install.html#linux-compose

It works GitHub Actions and act.

- run: sudo curl -L https://github.com/docker/compose/releases/download/1.16.1/docker-compose-`uname -s`-`uname -m` -o /usr/local/bin/docker-compose
- run: sudo chmod +x /usr/local/bin/docker-compose

[alexey2baranov]

Another way is to create additional action setup-docker-compose like we have setup-node which is responsible for docker-compose installation

and this action can internally perform docker-compose --version to skip himself if docker-compose installed already. or it can internally check enverounment env=REAL_GITHUB_ACTION_IMAGE to skip himself.

I think it is more general way then create new image because it don't need to recreate image every time when base image changed.

[adrienjoly]

On my Mac with M1 chip, I have to:

• install docker-compose, as suggested by @hata6502, cf docker-compose: command not found #112 (comment)
• and specify the platform, as suggested by @visini, cf docker-compose: command not found #112 (comment)
• and use the linux/amd64 architecture

=> $ act --platform ubuntu-latest=lucasalt/act_base:latest --container-architecture linux/amd64

EDIT: Actually, my workflow relies on ubuntu-20.04 instead of ubuntu-latest, so I'm using:

$ act --platform ubuntu-20.04=lucasalt/act_base:latest --container-architecture linux/amd64

[adrienjoly]

Medium images already contain docker-compose

I did pick the Medium image on first act run (see the image name below, as listed on https://github.com/nektos/act#runners), and got docker-compose: command not found anyway:

Here's the workflow file: https://github.com/openwhyd/openwhyd/blob/master/.github/workflows/ci.yml#L308

[aucampia]

is there any workaround for this?

[topherfangio]

Here's how I got it working.

First, make sure your Docker installation has enough space (I was maxed out at 60GB, so I doubled it to 120GB just to be safe.

Then, use Docker pull to grab the full image (15GB):

docker pull ghcr.io/catthehacker/ubuntu:full-latest

Now you can use this as your platform when starting act:

act -P ubuntu-latest=ghcr.io/catthehacker/ubuntu:full-latest -j my-job

One last note: I had to update my commands to use sudo so that it had enough permissions to run everything. Would love to know if there is a way to tell act to do this.

Here is an excerpt from my workflow:

name: Linting

on: [pull_request]

jobs:

  lint-api:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout
        uses: actions/checkout@v2

      - name: Create necessary files
        run: sudo touch .env.development.local

      - name: Start the container
        run: sudo docker-compose up --build -d api

      - name: Check Bundle
        run: sudo docker-compose exec -T api bundle install

      - name: Run rubocop
        run: sudo docker-compose exec -T api bundle exec rubocop

      - name: Dump docker logs on failure
        if: failure()
        uses: jwalton/gh-docker-logs@v1

Hope this helps someone in the future!

And shoutout to @catthehacker for his suggestion to run the docker pull command first 🙌 This allows you to see a progress bar of how the download and extraction is going.

[yambottle]

Tried with the Large image act -P ubuntu-latest=ghcr.io/catthehacker/ubuntu:full-latest, but having permission denied while running actions/create-release@v1. #935 Comment

Since the Medium image act -P ubuntu-latest=ghcr.io/catthehacker/ubuntu:act-latest doesn't have permission denied issue, decided to extend the image by myself.

custom-medium.Dockerfile

# docker build -f custom-medium.Dockerfile -t drewyangdev/ubuntu:act-latest .
FROM ghcr.io/catthehacker/ubuntu:act-latest

RUN curl -L "https://github.com/docker/compose/releases/download/1.29.2/docker-compose-$(uname -s)-$(uname -m)" -o /usr/local/bin/docker-compose && \
    chmod +x /usr/local/bin/docker-compose && \
    ln -s /usr/local/bin/docker-compose /usr/bin/docker-compose && \
    docker-compose --version

act -P ubuntu-latest=drewyangdev/ubuntu:full-latest

[sneko]

I was about to use the runner image from @LucasCtrl but the latest version is from 2020 and it's hard to assume act did not bring improvements since then.

Except if there is a watcher for act images that rebuild one with docker-compose, I won't go this way.

The solution I use for now:

      - uses: KengoTODA/actions-setup-docker-compose@v1
        if: ${{ env.ACT }}
        name: Install `docker-compose` for local simulations
        with:
          version: '2.14.2'

(specify the version otherwise the action will require you providing a valid GITHUB_TOKEN)