Follow the build logs - Githubissues

plasmabio / tljh-repo2docker

Plugin for The Littlest JupyterHub to build multiple user environments with repo2docker

BSD 3-Clause "New" or "Revised" License

60 stars 15 forks source link

Follow the build logs #5

Closed jtpio closed 4 years ago

jtpio commented 4 years ago

Similar to BinderHub, it would be useful to be able to follow the build logs after adding a new image:

We should look into reusing some parts of the BinderHub frontend, especially the one that uses xterm.js to display the logs. A couple of links:

the BinderImage abstraction, that would hide implementation details such as the use of an EventSource
building a new Terminal to show the logs

Also the build endpoint could follow the one from BinderHub and emit events.

pierrepo commented 4 years ago

Hi @jtpio I totally agree. Logs are also usefull for the end user to indicate that something is doing something somewhere.

pierrepo commented 4 years ago

Will it be possible to also store this log as a file on the server? This file should be accessible only to the admin through SSH connexion onto the server, for post-mortem analysis.

jtpio commented 4 years ago

Will it be possible to also store this log as a file on the server? This file should be accessible only to the admin through SSH connexion onto the server, for post-mortem analysis.

Since repo2docker is started in its own Docker container, it should be possible to retrieve the logs, maybe by mounting a volume from the host and telling repo2docker to log there.

jtpio commented 4 years ago

Although just like Binder, the way to troubleshoot build issues at the moment would be to run repo2docker locally (or on the server directly after SSHing), which would give access to the logs.