Closed StefanLelieveld closed 4 months ago
Thanks @StefanLelieveld . If we go this route I'd also like to automate this with github actions.
Alternatively, I'm wondering why would we still maintain this instead of pointing to the biocontainer that bioconda builds automatically? then all we have to do is change all the paths to quay.io/biocontainers/insilicoseq:2.0.0--pyh7cba7a3_0
in the documentation.
Lemme know what you think /Hadrien
Thanks @StefanLelieveld . If we go this route I'd also like to automate this with github actions.
Alternatively, I'm wondering why would we still maintain this instead of pointing to the biocontainer that bioconda builds automatically? then all we have to do is change all the paths to
quay.io/biocontainers/insilicoseq:2.0.0--pyh7cba7a3_0
in the documentation.Lemme know what you think /Hadrien
Hi Hadrien,
I just had a chat with Thijs and we like the alternative approach you propose. I will remove the Dockerfile + docker-build.sh and change the docker-image in the README to the biocontainer docker-image you provided.
best, Stefan
I will remove the Dockerfile + docker-build.sh and change the docker-image in the README to the biocontainer docker-image you provided.
Update on the matter: The Biocontainer docker image is not build for the ARM architecture (only for AMD?). This might be a reason to use the Dockerfile (and multi-arch build script) to provide support for both architectures in one solution.
@HadrienG @ThijsMaas what would your opinion? Support ARM architectures too?
We're a pure python package. The biocontainer works on my ARM mac despite being built for amd64
Issue: Docker-image is not working correctly for v2.0.0 (locally). And is not working on https://hub.docker.com/r/hadrieng/insilicoseq