Closed ezherman closed 8 months ago
I am having the same issue. Using your fork for now @ezherman, this solves it.
same issue here, last week it was working now not anymore.
Could be possible to do not pull the latest version? Since my workflow has not been locally tested with snakemake v8
From snakemake v8 the docker parent image is mambaorg/micromamba, which does not include conda/mamba. I could verify by adding a stagein section:
- name: Test workflow
uses: snakemake/snakemake-github-action@v1.25.1
with:
directory: .test
snakefile: workflow/Snakefile
stagein: micromamba config append channels conda-forge; micromamba install -n snakemake -y rsync conda mamba
in one of my workflows.
Indeed, sorry for the issue, my mistake. I have added mamba to the container here: https://github.com/snakemake/snakemake/commit/eb0c88495b506300fdf7c1afc4c02d6b91c6a582 The next release will fix the issue.
Fixed with Snakemake 8.1 that has just been released.
Apart from that, it would be great to allow selecting a specific Snakemake version via the action arguments. I think this can be achieved in one pass with migrating this into a composite action that simply installs Snakemake and mamba via the micromamba action instead of using a container.
It appears that with the stable docker build, conda is not properly installed.
I am getting the following output at the testing stage, from the
main
branch of this example repo:With Snakemake set to v7.32.0 through a modified fork of this repository (see this branch), things run fine:
The relevant actions can be found here: