Skip to content

Commit

Permalink
thanks for the help
Browse files Browse the repository at this point in the history
  • Loading branch information
hexylena committed Oct 30, 2024
1 parent bec9b36 commit 0147a7a
Show file tree
Hide file tree
Showing 2 changed files with 6 additions and 2 deletions.
4 changes: 4 additions & 0 deletions CONTRIBUTORS.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -2397,6 +2397,10 @@ TanguyGen:
name: Tanguy Genthon
joined: 2023-06

thanhleviet:
name: Thanh Le Viet
joined: 2024-10

themudo:
name: Gonçalo Themudo
joined: 2021-10
Expand Down
4 changes: 2 additions & 2 deletions topics/admin/faqs/galaxy-jobs-in-containers.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@ title: How can I get my container requiring jobs to run in a container?
area: galaxy
box_type: tip
layout: faq
contributors: [hexylena]
contributors: [hexylena, thanhleviet]
---

Some tools will only run in a container, i.e. they have a container defined in the 'requirements' section of the tool's XML file.
Expand All @@ -15,7 +15,7 @@ You can resolve this by configuring your job conf to have destinations that supp

The destination must have `docker_enabled` (Or `singularity_enabled`), and you can consider adding `require_container` to make sure the job will fail if the container isn't available. The `docker_volumes` string will allow you to control which volumes are attached to that container;

In TPV this would look like:
In TPV configuration (provided by @gtn:thanhleviet) this would look like:

```yaml
docker:
Expand Down

0 comments on commit 0147a7a

Please sign in to comment.