Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

framework: new docker image based on Debian Stretch #3569

Merged
merged 1 commit into from
Feb 16, 2019

Conversation

ymartin59
Copy link
Contributor

Motivation: Get recent Meson to build recent fuse for sshfs (synocli-net)

Docker image is far lighter that previous one on Jessie because I discarded most documentation tooling (mainly latex) with --no-install-recommends

@ymartin59
Copy link
Contributor Author

Mercurial built with that image.

@ymartin59
Copy link
Contributor Author

@m4tt075 I am interested in feedback about this new docker image - if you may run it for your future local builds (ffmpeg, tvendhead...)

@m4tt075
Copy link
Contributor

m4tt075 commented Jan 11, 2019

Oh yes. And this is most likely what I'd need to meet the CMake 3.1+ dependency in #3575. Unfortunately, I can't use Docker locally and test this, but is there a docker pull command to tell travis to pull this dockerfile instead of from synocommunity/spksrc?

@ymartin59
Copy link
Contributor Author

I am intrigued about "I can't use Docker locally"... Is there any way I may help about it?

You may use "docker build -t synocommunity/spksrc:stretch - < Dockerfile" command to create image "spksrc:stretch" BUT I hope travis may have some caching mechanism to avoid building that 700 MiB image each time...

@ymartin59
Copy link
Contributor Author

If I understand well, you run Linux in Virtual Box - so there is no technical reason why you may not install "docker" package in your Linux distribution to test that image.

@ymartin59
Copy link
Contributor Author

... ffmpeg is building - I guess it means a "OK" for this image ... but I guess I have to request @Diaoul for grants to push a new image into Docker Hub.

@m4tt075
Copy link
Contributor

m4tt075 commented Jan 12, 2019

@ymartin59 I tried to install docker locally some time ago, but it would have required me to change BIOS options that I use for VirtualBox. I've been reluctant to do that so far. I'll maybe try again in the future. My interest yesterday was to point travis at your image. If I understood correctly, for that it needs to be registered on some server though. To that extent, it would be phantastic if @Diaoul could grant you the permission to push it into the hub...

@Diaoul
Copy link
Member

Diaoul commented Jan 14, 2019 via email

@Diaoul
Copy link
Member

Diaoul commented Jan 14, 2019

If this gets merged the image will automatically be published on Docker Hub as it is an automated build. Do you need both images?

@ymartin59
Copy link
Contributor Author

ymartin59 commented Jan 14, 2019 via email

@Diaoul
Copy link
Member

Diaoul commented Jan 14, 2019

It seems it's not possible to tag from Docker Hub. Give me your Docker id here or by email, I'll grant you permission.

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.

3 participants