Added RunTime set of images that are slimmer and a jupyter bonus#68
Added RunTime set of images that are slimmer and a jupyter bonus#68aloysbaillet wants to merge 133 commits intoAcademySoftwareFoundation:mainfrom
Conversation
Signed-off-by: Aloys Baillet <aloys.baillet+github@gmail.com>
jfpanisset
left a comment
There was a problem hiding this comment.
Seems super useful, and USD in a Jupyter notebook is definitely very cool.
Signed-off-by: Aloys Baillet <aloys.baillet+github@gmail.com>
Signed-off-by: Aloys Baillet <aloys.baillet+github@gmail.com>
136fdf2 to
ed1b190
Compare
|
I've been experimenting with adding a real Xorg instance inside the docker container, with an extra I've been trying to research ways of starting Xorg without TTY but so far no luck... |
jfpanisset
left a comment
There was a problem hiding this comment.
Looks good, the xpra stuff is intriguing, I had not heard about it before. Running Xorg inside of a container seems like one of those "why would you want to do that?" requirements since in most scenarios you have control over how you start the container, and are able to run X11 outside the container(s). I wonder if there's a way to get xpra to forward pixels being rendered to a surface allocated via EGL without having X11 involved?
|
I'm going to try what Qt can do with EGL and without X11... having Qt to abstract things around might be quite useful with PySide and Jupyter (see the usdrecord snippet that needs a Qt app and a QGLWidget). |
Signed-off-by: Thomas Mansencal <thomas.mansencal@gmail.com>
Signed-off-by: Simran Brucherseifer <simran.brucherseifer@gmail.com>
Signed-off-by: Simran Brucherseifer <simran.brucherseifer@gmail.com>
Signed-off-by: Simran Spiller <simran.spiller@gmail.com>
Signed-off-by: Simran Spiller <simran.spiller@gmail.com>
Signed-off-by: Simran Spiller <simran.spiller@gmail.com>
Signed-off-by: Simran Spiller <simran.spiller@gmail.com>
Signed-off-by: Simran Spiller <simran.spiller@gmail.com>
Signed-off-by: Simran Spiller <simran.spiller@gmail.com>
Signed-off-by: Simran Spiller <simran.spiller@gmail.com>
Signed-off-by: Aloys Baillet <aloys.baillet+github@gmail.com>
Signed-off-by: Aloys Baillet <aloys.baillet+github@gmail.com>
Signed-off-by: Aloys Baillet <aloys.baillet+github@gmail.com>
Signed-off-by: Aloys Baillet <aloys.baillet+github@gmail.com>
Signed-off-by: Aloys Baillet <aloys.baillet+github@gmail.com>
Signed-off-by: Aloys Baillet <aloys.baillet+github@gmail.com>
Signed-off-by: Aloys Baillet <aloys.baillet+github@gmail.com>
Signed-off-by: Aloys Baillet <aloys.baillet+github@gmail.com>
Signed-off-by: Aloys Baillet <aloys.baillet+github@gmail.com>
Signed-off-by: Aloys Baillet <aloys.baillet+github@gmail.com>
Signed-off-by: Aloys Baillet <aloys.baillet+github@gmail.com>
Signed-off-by: Aloys Baillet <aloys.baillet+github@gmail.com>
Signed-off-by: Aloys Baillet <aloys.baillet+github@gmail.com>
Signed-off-by: Aloys Baillet <aloys.baillet+github@gmail.com>
Signed-off-by: Aloys Baillet <aloys.baillet+github@gmail.com>
Signed-off-by: Aloys Baillet <aloys.baillet+github@gmail.com>
If you try to use shell scripts to install packages directly, e.g. in a location other than /usr/local, a couple of them cause problems. In build_pyside.sh, don't try to create /tmp/qt5temp/bin/qt.conf if the user has not in fact moved Qt to /tmp/qt5temp. In build_usd.sh, specify GLEW_LOCATION explicitly. Signed-off-by: Geoff Levner <glevner@gmail.com>
Signed-off-by: Geoff Levner <glevner@gmail.com>
Signed-off-by: Aloys Baillet <aloys.baillet+github@gmail.com>
Signed-off-by: Aloys Baillet <aloys.baillet+github@gmail.com>
Signed-off-by: Aloys Baillet <aloys.baillet+github@gmail.com>
Signed-off-by: Aloys Baillet <aloys.baillet+github@gmail.com>
Signed-off-by: Aloys Baillet <aloys.baillet+github@gmail.com>
Signed-off-by: Aloys Baillet <aloys.baillet+github@gmail.com>
Signed-off-by: Aloys Baillet <aloys.baillet+github@gmail.com>
Signed-off-by: Aloys Baillet <aloys.baillet+github@gmail.com>
Signed-off-by: Aloys Baillet <aloys.baillet+github@gmail.com>
Signed-off-by: Aloys Baillet <aloys.baillet+github@gmail.com>
Signed-off-by: Aloys Baillet <aloys.baillet+github@gmail.com>
Signed-off-by: Aloys Baillet <aloys.baillet+github@gmail.com>
Signed-off-by: Aloys Baillet <aloys.baillet+github@gmail.com>
Signed-off-by: Aloys Baillet <aloys.baillet+github@gmail.com>
Signed-off-by: Aloys Baillet <aloys.baillet+github@gmail.com>
Signed-off-by: Aloys Baillet <aloys.baillet+github@gmail.com>
jfpanisset
left a comment
There was a problem hiding this comment.
This review might get invalidated when you update this branch, but this still looks like really useful functionality. Does it need some notes in README.md to explain the purpose of CI vs RT images?
|
Thanks JF, indeed I'll make sure I add more info in the readme once the images are ready! |
This is a "working draft" of a new set of ASWF docker images for "run-time" instead of CI. They are slimmer and only contain the build artifacts without any compiler.

rt-vfxallis around 1.8GB whenci-vfxallis 2.6GB.I've added a
rt-vfxall-jupyterthat contains a Jupyter notebook that is able to access full USD and GPUs, as shown in this screenshot:(To run:
docker run -it --rm --gpus=all -e DISPLAY=$DISPLAY -v /tmp/.X11-unix:/tmp/.X11-unix:rw -v ~/Downloads/Kitchen_set:/home/jovyan/work -p 8888:8888 aswftesting/rt-vfxall-jupyter:2020)I feel that these images should be quite generally useful as well, and probably easier to understand than the CI ones.
Any thoughts?