Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/davidk/docker-slic3r-prusa3d

PrusaSlicer in a Docker container (Prusa3D's Slic3r fork) - Automated Docker Hub tags/rebuilds/updates via GitHub Actions
https://github.com/davidk/docker-slic3r-prusa3d

docker prusa3d slic3r

Last synced: about 1 month ago
JSON representation

PrusaSlicer in a Docker container (Prusa3D's Slic3r fork) - Automated Docker Hub tags/rebuilds/updates via GitHub Actions

Awesome Lists containing this project

README 

        
# docker-prusaslicer



This repository tracks and containerizes [Prusa3D's PrusaSlicer](https://github.com/prusa3d/PrusaSlicer). The files here contain the Dockerfile, supporting scripts and instructions for usage.



![PrusaSlicer GUI running in a Docker container](img/prusaslicer-in-docker.png)



If you're looking for a regular build of PrusaSlicer, the latest builds are available on PrusaSlicer's [releases page](https://github.com/prusa3d/PrusaSlicer/releases).



To grab and run PrusaSlicer as a container (in GUI mode)



    docker run --net=host \

    -v /tmp/.X11-unix:/tmp/.X11-unix \

    -v $PWD:/Slic3r/3d:z \

    -v slic3rSettings:/home/slic3r \

    -e DISPLAY=$DISPLAY \

    --rm keyglitch/docker-slic3r-prusa3d



PrusaSlicer can also be run without the GUI, for slicing via scripts, etc. The [slic3r-action repository](https://github.com/davidk/slic3r-action) is an example of this usage. 



## Container notes



* Your current directory will be mounted into the container at /Slic3r/3d (change the :z option as appropriate to :rw/:ro).



* Settings are persisted into the slic3rSettings volume.



* Fedora users: SELinux might block access to X by slic3r inside the container. Look in /var/log/messages or /var/log/audit/audit.log to see if this is happening (and for the relevant commands to fix).



* Alternatively, there might be a permission error upon trying to access X. Try running `xhost local:root` to fix (this is a temporary fix and must be reapplied when restarting the host).



Sample error example:



    No protocol specified

    19:13:54: Error: Unable to initialize GTK+, is DISPLAY set properly?

    Failed to initialize wxWidgets at /Slic3r/slic3r-dist/lib/site_perl/5.22.0/Slic3r/GUI/2DBed.pm line 10.

    Compilation failed in require at /Slic3r/slic3r-dist/lib/site_perl/5.22.0/Slic3r/GUI/2DBed.pm line 10.

    BEGIN failed--compilation aborted at /Slic3r/slic3r-dist/lib/site_perl/5.22.0/Slic3r/GUI/2DBed.pm line 10.

    Compilation failed in require at /Slic3r/slic3r-dist/lib/site_perl/5.22.0/Slic3r/GUI.pm line 9.

    BEGIN failed--compilation aborted at /Slic3r/slic3r-dist/lib/site_perl/5.22.0/Slic3r/GUI.pm line 9.

    Compilation failed in require at (eval 87) line 1.



## Building the latest release locally



If the hub version is ever out of date (or for any other reason), it is possible to build an image locally. `getLatestPrusaSlicerRelease.sh` will automatically try to get the latest non-AppImage version through the GitHub API during the build process.



Building:



    $ docker build -t docker-slic3r-prusa3d .

    Sending build context to Docker daemon 73.73 kB

    [ .. truncated ..]



## Convenience Script



A [small script](https://raw.githubusercontent.com/davidk/docker-slic3r-prusa3d/master/slic3r.sh) wraps the `docker run` command above. It also contains a commented out snippet for poking around the persistent volume.



### Example



    $ echo $PATH

    /usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/home/davidk/.local/bin:/home/davidk/bin

    $ cp slic3r.sh /home/davidk/.local/bin/slic3r

    $ chmod +x /home/davidk/.local/bin/slic3r

    $ slic3r