QuartusBuildVMs
QuartusBuildVMs copied to clipboard
docker images not automatically updated on dockerub
https://hub.docker.com/r/cdsteinkuehler/jessie-quartus-base/ shows old commits
dockerhub makes it easy to link to this github repo and trigger a rebuild on push so they'd be always up to date
that'd enable us to add a .travis dir to the mksocfpga repo so everybody could rebuild firmware
On 7/21/2016 6:05 PM, Michael Haberler wrote:
https://hub.docker.com/r/cdsteinkuehler/jessie-quartus-base/ shows old commits
dockerhub makes it easy to link to this github repo and trigger a rebuild on push so they'd be always up to date
that'd enable us to add a .travis dir to the mksocfpga repo so everybody could rebuild firmware
I don't think the automated builds allow for "squashing" the resulting image, which is required unless you want a 20+ GB docker file. :(
Charles Steinkuehler [email protected]
well we could setup an automated build on jenkins.machinekit.io then, plus push to dockerhub from there, would be good to have those images á jour explorting https://github.com/jwilder/docker-squash
On 7/22/2016 1:50 AM, Michael Haberler wrote:
well we could setup an automated build on jenkins.machinekit.io then, would be good to have those images á jour explorting https://github.com/jwilder/docker-squash
No experimeting necessary, see the step-by-step directions in the comments at the end of the Dockerfile.
I had bad luck using docker-squash, so I switched to docker-rebase:
Get the docker-rebase script from here:
https://github.com/docbill/docker-scripts
This keeps things like the USER setting from the original container, and doesn't fail on the (very large) Quartus build images.
Charles Steinkuehler [email protected]