Skip to content

Fixed Binder Dockerfile#1266

Merged
fkiraly merged 4 commits intosktime:mainfrom
corvusrabus:binder-dockerfile
Aug 12, 2021
Merged

Fixed Binder Dockerfile#1266
fkiraly merged 4 commits intosktime:mainfrom
corvusrabus:binder-dockerfile

Conversation

@corvusrabus
Copy link
Copy Markdown
Contributor

Reference Issues/PRs

Fixes #807
Fixes #662

What does this implement/fix? Explain your changes.

The Binder Dockerfile stopped working at some point. I changed the requirements files for the Docker file and it works now. The Docker file "compiles" and I ran the first example notebook in it.

I changed the base Docker image used because the one that is in the current Dockerfile is just an arbitrary one copied from the Binder docs. I think that the Jupyter Notebook Python 3.8 is a reasonable base image because it already contains some of the needed libraries and Python 3.8 is the newest version that can currently be used with Numba (according to my understanding).

This is not an optimal solution yet because something is broken with the way Prophet is being built but this can only be changed once the Prophet developers fix it. I know it is weird to have two requirement files but Prophet doesn't build without having some libraries installed first.

Does your contribution introduce a new dependency? If yes, which one?

No

What should a reviewer concentrate their feedback on?

For all contributions

@corvusrabus corvusrabus requested a review from mloning as a code owner August 8, 2021 21:11
Copy link
Copy Markdown
Collaborator

@fkiraly fkiraly left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Very nice, thanks!!

Didn't think I'd ever see the day where someone figures out what's wrong with our binder!
So it was prophet all along? Go figure.

You forgot to add yourself to .all-contributorsrc, though.

@fkiraly
Copy link
Copy Markdown
Collaborator

fkiraly commented Aug 8, 2021

This is not an optimal solution yet because something is broken with the way Prophet is being built but this can only be changed once the Prophet developers fix it.

But it's great because it works!
Which means it's no longer pessimal, and that's very much enough, thanks.

Copy link
Copy Markdown
Collaborator

@fkiraly fkiraly left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmmmm - it seems that binder works, but it somehow broke CI/CD (see test_examples below and the inability to run jupyter) - could you kindly check what is happening there?

@corvusrabus
Copy link
Copy Markdown
Contributor Author

Yes I noticed that the Github workflows use the binder requirements file to test the example files. I changed the workflow to include the second requirements file I added. I hope it passes the test now

Copy link
Copy Markdown
Collaborator

@fkiraly fkiraly left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks good to me now!

Would be great if you could have a look, @mloning, since you set up the binder originally

@fkiraly
Copy link
Copy Markdown
Collaborator

fkiraly commented Aug 12, 2021

so, it runs but there's stil the problem of not being able to build a prophet wheel (so it defaults to a legacy setup):

image

... any good ideas? All that red output may look scary for the typical user...

@mloning
Copy link
Copy Markdown
Contributor

mloning commented Aug 12, 2021

Thanks @corvusrabus for the fix - great work!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[BUG] binder notebook environment build breaks over scikit-posthocs unable to load pyqt5 in setup.py Binder build fails

3 participants