Maybe my image size or the memory footprint when building on Binder is too large. Then I’ll be happy if anyone advises me on what limits should I stick to? Any help is appreciated, thanks in advance!
To follow on that. @inpefess you can leave the rest of your repository ‘as-is’ and you can add a binder directory. Them MyBinder will use the configuration files in there for the MyBinder-specific launches. That way your others remain intact and you can try options without concern you’ll miss up other ways you or others use your repository contents. The documentation mentions it here:
" Configuration files may be placed in the root of your repository or in a binder/ folder in the repository’s root (i.e. myproject/binder/ )."
I’m using not a standard Jupyter image since I need to install a piece of software which is distributed only as a tarball or a Docker image. I guess I can use Configuration Files — Binder 0.1b documentation then, can’t I?
Oh sorry. I hadn’t picked up on how sporadic it is. It sounds like you were just testing your complex stuff at a time that MyBinder was having some more issues than usual. Resources are limited at several points and sometimes that causes different messages. The fact it works as it did means that there was nothing you can do about that issue you saw. Fortunately, it also means that nothing has changed to make the underlying process incompatible with your approach. Seems it was just bad timing.