This action uses the Machinefile executor to run Dockerfile/Containerfile commands directly on the host system without using Docker, Podman or any other container engine. It's useful for executing build commands in a predictable environment or setting up development tools.
steps:
- uses: actions/checkout@v3
- name: Run Machinefile commands
uses: gbraad-actions/machinefile-executor-action@v3
with:
containerfile: 'Containerfile' # or path to your Containerfile
context: '.' # Build context directory| Input | Description | Required | Default |
|---|---|---|---|
| containerfile | Path to the Dockerfile/Containerfile | Yes | 'Containerfile' |
| context | Directory to use as build context | Yes | '.' |
| arguments | Additional arguments to pass | No | '' |
| binarypath | Override the path of executor to use | No | '' |
| version | Version of executor binary to download | No | '0.5.0' |
Here's an example workflow that uses the Machinefile Executor to set up a development environment:
name: Build with Containerfile
on:
push:
branches: [ main ]
pull_request:
branches: [ main ]
jobs:
build:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
- name: Run Dockerfile commands
uses: gbraad-actions/machinefile-executor-action@v3
with:
containerfile: 'containers/Containerfile-devtools'
context: '.'
arguments: --arg=USER=gbraad
- name: Run build tests
run: |
# Your build commands here
make test- name: Setup with local runner
uses: gbraad-actions/machinefile-executor-action@main
with:
containerfile: Containerfile
context: .
runner: local- name: Setup with Podman runner
uses: gbraad-actions/machinefile-executor-action@main
with:
containerfile: Containerfile
context: .
runner: podman
podman-name: my-container
podman-connection: my-connection- name: Setup with SSH runner
uses: gbraad-actions/machinefile-executor-action@main
with:
containerfile: Containerfile
context: .
runner: ssh
ssh-host: example.com
ssh-user: user
ssh-key: ${{ secrets.SSH_PRIVATE_KEY }}
args: |
USER=gbraad
GROUP=wheel |
|---|
| @gbraad |