asked 2018-07-21 20:00:38 +0200
Hello !
For your delight, here is the Sailfish (platform) SDK packaged as a docker image. However, at the moment you have to build it yourself, as I'm unsure about if I have the rights to upload it to docker hub.
Check https://github.com/SfietKonstantin/docker-sailfishos-sdk for more information.
Tests are welcomed, and bugreports can be posted on the github repo.
answered 2018-08-13 17:09:57 +0200
Pushed to docker hub:
Will try to maintain it in future.
Well, i still not decided if it's better to have SailfishOS-latest target names, or SailfishOS-version ones. For CI it should be better to have latest, but at the same time it will be good to be sure you building for exact SailfishOS version, so, let's discuss this :) I am planning to update my repo for each new sdk release and set tag, so users can pull any sfos sdk version (if) they want.
Also I am planning to try to use this image for HADK stuff as well, requires more experiments here.
coderus ( 2018-08-14 09:40:06 +0200 )editWhat about tagging and use git tag to build a given version ? - Assume at current commit there is a tag & then you pass some flags to build script you build the image coresponding to tagged version - If no tag at current commit and / or not passed the argument to build tagged image, you build latest.
Sfiet_Konstantin ( 2018-08-14 20:08:51 +0200 )editanswered 2018-08-13 17:27:45 +0200
Also i made this: - https://github.com/CODeRUS/docker-sailfishos-sdk-local
Image can be used to build packages with Sailfish OS SDK (Qt Creator) instead of virtual machine. Some additional magic is needed (see: https://github.com/evilJazz/sailfishos-buildengine)
Is this way faster than the Virtual Machine one? Building big projects can take same time with the VM.
Dylan Van Assche ( 2018-08-13 22:42:54 +0200 )editYou might gain some minimal time by shaving off virtualized OS resource consumption.
Sfiet_Konstantin ( 2018-08-14 20:09:41 +0200 )editAsked: 2018-07-21 20:00:38 +0200
Seen: 1,006 times
Last updated: Aug 13 '18
this way is for creating kinda "readonly" image, like obs does. every rpm build will download build requires again, and changes inside image will not be persistent.
but it's good start for making base image, everyone can commit to new image with required changes.
coderus ( 2018-07-24 13:26:42 +0200 )edit@coderus, indeed, I desgined this image to be able to use in (eg) Jenkins CI.
What kind of persisted changes you are expecting ? Maybe we can see if there are always-installed packages to be included in the script, or build several flavours of the image.
Sfiet_Konstantin ( 2018-07-24 20:38:21 +0200 )editfor example sudo
coderus ( 2018-07-29 10:17:11 +0200 )editzypper in python-rpm lvm2 atruncate pigzis required to build firmware images using this container :)