hey @caravanuden ! Your container is stuck in running because the instance gets killed - I think likely the amount of files / downloads needed gets bigger than the actual server can allow and it's killed. What I can suggest is to make a base image that uses a multistage build and doesn't include the raw (space heavy) files. You can also find strategies to make the current image smaller (e.g., cleaning up as you go), or you can build entirely on Docker Hub and pull into a Singularity image.
What I'd recommend is rebuilding a version of the container that was previously okay (I triggered a build just now for the second to last commit), and then "freezing" on Singularity Hub. That way when you commit again it won't rebuild over the existing image. This is important so you always have a container there.
hey @caravanuden ! Your container is stuck in running because the instance gets killed - I think likely the amount of files / downloads needed gets bigger than the actual server can allow and it's killed. What I can suggest is to make a base image that uses a multistage build and doesn't include the raw (space heavy) files. You can also find strategies to make the current image smaller (e.g., cleaning up as you go), or you can build entirely on Docker Hub and pull into a Singularity image.
What I'd recommend is rebuilding a version of the container that was previously okay (I triggered a build just now for the second to last commit), and then "freezing" on Singularity Hub. That way when you commit again it won't rebuild over the existing image. This is important so you always have a container there.