GitHub Community
-
Select Topic AreaQuestion BodyHello there! I wonder if it's possible to mount a file from a repository to a service container's volume mount? Based on the docs
But if service containers are started before actually running the action steps, how should I set this up? |
Beta Was this translation helpful? Give feedback.
Replies: 16 comments 17 replies
-
|
That depends on what you actually want to achieve, as in which data (or directory) do you want to share with the service container? |
Beta Was this translation helpful? Give feedback.
-
|
Hi @airtower-luna, I tried For more contexts, I want to provide Selenium service using Selenium Grid in standalone mode and mount $GITHUB_WORKSPACE/target/Downloads to Downloads folder of Selenium container. After docker run, I tried to connect Selenium service using URL http://standalone-selenium:4444/ (I'm using --network-alias options to specify standalone-selenium), but failed to connect. Am I wrong or missing any step? |
Beta Was this translation helpful? Give feedback.
-
|
The |
Beta Was this translation helpful? Give feedback.
-
|
There are 2 containers here, job_container (using image MY_RUNNER_CONTAINER_IMAGE) and service_container (Selenium). Because I start service_contain by Updated: after testing, the connection is flaky. job_container failed to connect |
Beta Was this translation helpful? Give feedback.
-
|
Maybe the container takes a while to start up, and wasn't ready yet on the first attempt? If it's that, you might want to add a loop that probes if the container is ready, and waits a little if not before repeating the check. |
Beta Was this translation helpful? Give feedback.
-
|
Another suggestion: Try to mount the volume as "shared" (add suffix :z) |
Beta Was this translation helpful? Give feedback.
-
|
Just to add my $0.02 in the hopes that someone from github is watching: I agree that this does not currently seem to be possible, and it's a really bad limitation of the services product. An absolutely bog-standard pattern you'll see when using docker for CI work is that the docker image will look for run-time configuration files in a standard place, so that you can just mount them into the container. A more or less canonical example of this is the official Postgres docker image: the container will on startup execute any .sh or .sql files that it finds in the directory /docker-entrypoint-initdb.d -- this is commonly used to ensure that all db migrations are applied before the container starts up. Not being able to do this with GHA services really restricts their utility. :( |
Beta Was this translation helpful? Give feedback.
-
|
Running into this right now. I really don't think GitHub knows what they are doing with Actions. It's the worst CI system I've had to deal with, but unfortunately it's the one that's natively integrated. |
Beta Was this translation helpful? Give feedback.
-
|
@n-oden We recently worked around that, albeit with MySQL. We just have the step:
Nothing groundbreaking, but the idea may help someone. |
Beta Was this translation helpful? Give feedback.
-
|
Agreed. For our use case, we need to publish pre-seeded database containers to use for non-prod environments. Typically with something like mysql we'd do this by running a mysql service while allowing |
Beta Was this translation helpful? Give feedback.
-
|
I have a similar use case. I am migrating a docker-compose over to service containers. All the config files for testing are in the repo and are required to be mounted into the containers. The workaround of running the containers manually along with the bridge network makes the workflow messy. Abstracting it to an action keeps it clean but I would much prefer to use the |
Beta Was this translation helpful? Give feedback.
-
|
I also have similar usecase. I want to perform checkout repo before I can start service container. |
Beta Was this translation helpful? Give feedback.
-
|
I am running into this issue now. My previous team used git-labs and this was 100% possible. It was possible with Bitbucket also. We are going to use |
Beta Was this translation helpful? Give feedback.
-
|
I'm surprised this is still an issue. We're also affected by this. There's all sorts of edge cases with a manual docker run like making sure you don't accidentally leak credentials, waiting for the service to be healthy, etc. |
Beta Was this translation helpful? Give feedback.
-
|
I've found it's actually much simpler to use a docker-compose configuration to run services, define dependencies, wait for service health, env var configuration for containers, etc. It keeps the pipeline syntax clean and offers a more familiar, less verbose and syntaxtually clean approach. |
Beta Was this translation helpful? Give feedback.
-
|
@bkuhl Are you still using it? How do you wait for services to get ready? |
Beta Was this translation helpful? Give feedback.
-
|
For a standard PHP application, I create a compose service that'll actually run the task I need (in this case integration tests), and use compose to handle dependencies, config, startup, etc. Then in GHA, all I need to do is: |
Beta Was this translation helpful? Give feedback.
-
|
I've been using the following workaround to do this for a couple years now, but I can't seem to find the original link where I got the idea/syntax, which is what led me to this thread. If it helps anyone, here are my snippets. In this case, I'm using the Mosquitto MQTT service for integration tests, and want to mount configuration and password files rather than disabling authentication. The build runs in a Go container (may not be relevant): The MQTT service container is started: Nothing is populated yet due to lack of checkout. After checkout, the service container is restarted with this step: Tests now proceed correctly with the mounted file(s). |
Beta Was this translation helpful? Give feedback.
-
|
THANKS!!!! |
Beta Was this translation helpful? Give feedback.
-
|
Great advice. But - checkout has to use path else checkout will fail on the bindmount directory during initial cleanup steps:
- uses: actions/checkout@master
with:
path: coderun - use working-directory … - name: install deps
working-directory: ./code
run: |and writing to the volume from the runner requires sudo - name: install deps
working-directory: ./code
run: |
sudo unzip $HOME/www-data/DSP2043_2024.1.zip "public-rackmount1/*" -d ${{ github.workspace }}/tmp/DSP8010/public-rackmount1 |
Beta Was this translation helpful? Give feedback.
-
|
I haven't needed any of those settings for my builds to run and clean up successfully, but I'm glad you found a configuration that works for you! |
Beta Was this translation helpful? Give feedback.
-
|
I've had the volume mounted to Accessing the volumed mounted directory without sudo And I was unable to copy from the ${{ runner.temp }} to the container But - it's even worse, in my case the service container does not start when provided an initial empty volume directory, health check fails, pipeline fails. name: Codecov
on: [push, pull_request]
jobs:
run:
services:
mockup:
image: dmtf/redfish-mockup-server:latest
volumes:
- ${{ github.workspace }}/tmp/DSP8010/public-rackmount1:/tmp/public-rackmount1
options: --name mockup
ports:
- 8000:8000
steps:
- uses: actions/checkout@master
with:
path: code
- name: service::mock - unzip DSP8010 public-rackmount1
run: |
mkdir -p ${{ github.workspace }}/tmp/DSP8010/public-rackmount1
ls -al ${{ github.workspace }}/tmp/DSP8010/public-rackmount1
sudo unzip $HOME/www-data/DSP2043_2024.1.zip "public-rackmount1/*" -d ${{ github.workspace }}/tmp/DSP8010/
- name: service::mock - copy service files
uses: docker://docker
with:
args: docker container exec mockup cp -a /tmp/public-rackmount1 /usr/src/app/
- name: service::mock - restart to feed the volume
# https://github.com/orgs/community/discussions/42127#discussioncomment-7591609
uses: docker://docker
with:
args: docker restart mockup
- name: Generate coverage report (mock)
working-directory: ./code
run: |
pdm run pytest …
|
Beta Was this translation helpful? Give feedback.
-
|
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
-
|
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
-
|
I also just hit this and it is really really annoying. I'm simply trying to mount an nginx.conf file into nginx container. Feels like a common thing. |
Beta Was this translation helpful? Give feedback.
-
|
Also ran into this today |
Beta Was this translation helpful? Give feedback.
-
|
Run into this issue today. I tried to pass confirugration to my service, and I see it can't be done the normal way. |
Beta Was this translation helpful? Give feedback.
-
|
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
-
|
Why isn't this a documented issue on GitHub workflows? |
Beta Was this translation helpful? Give feedback.
I've been using the following workaround to do this for a couple years now, but I can't seem to find the original link where I got the idea/syntax, which is what led me to this thread. If it helps anyone, here are my snippets. In this case, I'm using the Mosquitto MQTT service for integration tests, and want to mount configuration and password files rather than disabling authentication.
The build runs in a Go container (may not be relevant):
The MQTT service container is started: