-
Hi. From the logs, the network alias name: Unit tests
concurrency:
group: ${{ github.workflow }}-${{ github.ref }}
cancel-in-progress: true
on:
pull_request:
types: [ synchronize ]
jobs:
phpunitquick:
runs-on: ubuntu-22.04
timeout-minutes: 15
services:
application_dbmaster:
# Using this instead of official MySQL one for MYSQL_AUTHENTICATION_PLUGIN support
image: bitnami/mysql:8.0
env:
# Values from build/properties/default.properties
MYSQL_DATABASE: application_testing
MYSQL_ROOT_USER: application
MYSQL_PASSWORD: password123
MYSQL_ROOT_PASSWORD: password123
MYSQL_AUTHENTICATION_PLUGIN: mysql_native_password
ports:
- 3306:3306
options: --health-cmd="mysqladmin ping" --health-interval=10s --health-timeout=5s --health-retries=3
steps:
- run: mysqladmin ping -happlication_dbmaster -uapplication -ppassword123 Job log:
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
RTFM'ing myself. From docs: Running jobs on the runner machine When a job runs directly on a runner machine, the service running in the Docker container does not expose its ports to the job on the runner by default. You need to map ports on the service container to the Docker host. For more information, see "About service containers." |
Beta Was this translation helpful? Give feedback.
RTFM'ing myself. From docs:
Running jobs on the runner machine
When running jobs directly on the runner machine, you can access service containers using localhost: or 127.0.0.1:. GitHub configures the container network to enable communication from the service container to the Docker host.
When a job runs directly on a runner machine, the service running in the Docker container does not expose its ports to the job on the runner by default. You need to map ports on the service container to the Docker host. For more information, see "About service containers."