# Simple Bash Computing environment

**URL:** <https://community.seqera.io/t/simple-bash-computing-environment/456>\
**Category:** Ask for help\
**Tags:** platform\
**Created:** [February 3, 2024, 8:17pm UTC](https://community.seqera.io/t/simple-bash-computing-environment/456 "2024-02-03T20:17:14Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![arnaudceol](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/arnaudceol/32/913_2.png) [@arnaudceol](https://community.seqera.io/u/arnaudceol)\
**Post date:** [February 3, 2024, 8:17pm UTC](https://community.seqera.io/t/simple-bash-computing-environment/456/1 "2024-02-03T20:17:14Z")

</div>

I would like to be able to launch jobs directly on share workstations without having to install a scheduler. Nextflow should simply run the job as “local” instead of “slurm”, “pbs”, etc… This feature would be extremely useful as it would help managing those workstation (I would create a workspace for each one) without having to provide access to each user. It would work either with ssh or tw agent. I proposed this feature to seqera, but maybe there is some way to do it that I missed.

---

<div class="post-metadata">

**Author:** ![ewels](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/ewels/32/1_2.png) [@ewels](https://community.seqera.io/u/ewels)\
**Post date:** [February 3, 2024, 11:54pm UTC](https://community.seqera.io/t/simple-bash-computing-environment/456/2 "2024-02-03T23:54:53Z")

</div>

What happens if you set the `executor` to `local` in a config? I don’t think I’ve ever tried it. Might be that it works, and it doesn’t matter that you set the compute environment up as Slurm even though Slurm isn’t available.

---

<div class="post-metadata">

**Author:** ![jordeu](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/jordeu/32/90_2.png) [@jordeu](https://community.seqera.io/u/jordeu)\
**Post date:** [February 4, 2024, 5:28am UTC](https://community.seqera.io/t/simple-bash-computing-environment/456/3 "2024-02-04T05:28:20Z")

</div>

AFAIK there is no official support for launching local executor from Seqera platform. See [this](https://github.com/seqeralabs/nf-tower/issues/331) issue for more details.

The only current solutions are:

- To install a single machine scheduler ([using docker](https://hpckp.org/articles/how-to-use-the-slurm-simulator-as-a-development-and-testing-environment/) may not be that difficult)
- Using the local executor and creating some Slurm [fake scripts](https://github.com/seqeralabs/nf-tower/issues/331#issuecomment-1032510322). I also did some fake scripts to submit and monitor jobs to a HyperQueue scheduler, which is a very easy-to-install solution if you want to use just a few workstations.

These workarounds should work with the Agent and when directly using an SSH connection.

---

<div class="post-metadata">

**Author:** ![arnaudceol](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/arnaudceol/32/913_2.png) [@arnaudceol](https://community.seqera.io/u/arnaudceol)\
**Post date:** [February 5, 2024, 9:35am UTC](https://community.seqera.io/t/simple-bash-computing-environment/456/4 "2024-02-05T09:35:29Z")

</div>

Thanks @jordeu , docker installation may be a good way to do this. Probably we should need a docker in docker image, and add aliasaes (`alias sinfo="docker exec -ti ${USER}_simulator sinfo"` etc.). I’ll have a try.

---

<div class="post-metadata">

**Author:** ![ewels](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/ewels/32/1_2.png) [@ewels](https://community.seqera.io/u/ewels)\
**Post date:** [March 8, 2024, 9:03am UTC](https://community.seqera.io/t/simple-bash-computing-environment/456/5 "2024-03-08T09:03:00Z")

</div>

For any future googlers: there is a feature request to track this here:

> **[Add support for "local" compute environment | Seqera Platform Feature Requests...](https://feedback.seqera.io/feature-requests/p/add-support-for-local-compute-environment)**
>
> I want to launch jobs directly on shared workstations without having to install a scheduler. Nextflow should simply run the job as "local" instead of "slurm",

Please add your votes if this is important to you, and you’ll be able to track any progress there. Thanks!

---

<div class="post-metadata">

**Author:** ![arnaudceol](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/arnaudceol/32/913_2.png) [@arnaudceol](https://community.seqera.io/u/arnaudceol)\
**Post date:** [September 13, 2024, 8:10am UTC](https://community.seqera.io/t/simple-bash-computing-environment/456/6 "2024-09-13T08:10:34Z")

</div>

To follow up on @jordeu proposal, this is what we are doing now. We extended the docker slurm image with the tower agent, this is working fine.