{"id":672,"date":"2014-03-29T13:14:08","date_gmt":"2014-03-29T12:14:08","guid":{"rendered":"http:\/\/katastrophos.net\/andre\/blog\/?p=672"},"modified":"2015-09-26T12:50:43","modified_gmt":"2015-09-26T10:50:43","slug":"running-sailfishos-build-engine-outside-virtualbox-vm","status":"publish","type":"post","link":"https:\/\/katastrophos.net\/andre\/blog\/2014\/03\/29\/running-sailfishos-build-engine-outside-virtualbox-vm\/","title":{"rendered":"Running the SailfishOS Build engine outside of a VirtualBox VM"},"content":{"rendered":"

I have been struggling with the SailfishOS Build Engine VM for quite some time. 4 out of 5 SailfishOS builds of QuasarMX would fail because the Shared Folder (vboxsf) mechanism in VirtualBox at some point starts to corrupt files on my system, even though the system’s RAM and storage are perfectly fine. Since QuasarMX heavily relies on qmlpp (see previous post<\/a>) to work with QtQuick 2, a lot of files will be touched during compilation. For this, vboxsf is both unreliable and slow (!).<\/p>\n

So, here is a short tutorial that will show how to run the SailfishOS Build engine outside of the VirtualBox VM in your host’s Linux installation. This guide is geared towards Ubuntu 12.04, but might work on other systems too.<\/p>\n

UPDATE 1: New version with root check, private namespace and permission fixes in SB2 targets.
\nUPDATE 2: The tutorial has been updated to work with SDK Alpha-1404 (Alpha 4). This new version does not work with Alpha-1312 (Alpha 3).
\nUPDATE 3: This method is working with SDK Beta-1509.<\/strong><\/p>\n

Start the Build engine VM and make sure you can connect to it via SSH (see Developer FAQ<\/a> for details):
\n$SUDO_USER is the username you used to sudo into root privileges, change it if you have not used sudo to become root.<\/p>\n

\r\nssh -p 2222 -i \/home\/$SUDO_USER\/SailfishOS\/vmshare\/ssh\/private_keys\/engine\/root root@localhost\r\n<\/pre>\n
If it works:<\/p>\n
\r\nexit\r\n<\/pre>\n
Now, become root:<\/p>\n
\r\nsudo -i\r\n<\/pre>\n
Create a directory to host the rootfs of the SailfishOS Build engine:<\/p>\n
\r\nmkdir \/opt\/sailfishos-buildengine\r\n<\/pre>\n
Use rsync to copy the rootfs to our newly created directory:<\/p>\n
\r\nrsync --numeric-ids -xazuv -e \"ssh -p 2222 -i \/home\/$SUDO_USER\/SailfishOS\/vmshare\/ssh\/private_keys\/engine\/root\" root@localhost:\/ \/opt\/sailfishos-buildengine\r\n<\/pre>\n
This will take a while. Go, have dinner or get a cup of tea.<\/p>\n
Save the following script as file “run-sailfishos-buildengine.sh” somewhere you like. We’ll use \/opt\/run-sailfishos-buildengine.sh
\nMake sure to edit the first few lines to match your environment, SDK=\/opt\/SailfishOS is the directory you used to install the Sailfish SDK on your host. This probably is \/home\/YOURUSERNAME\/SailfishOS if you haven’t installed as root.<\/p>\n
\r\n#!\/bin\/bash\r\nUSER=$SUDO_USER\r\nUSERDIR=\/home\/$USER\r\nSDK=\/opt\/SailfishOS\r\nBUILDENGINE=\/opt\/sailfishos-buildengine\r\n\r\nif [ $EUID -ne 0 ]; then\r\n\techo "This script must be run as root." 1>&2\r\n\texit 1\r\nfi\r\n\r\nif cmp -s \/proc\/$PPID\/mountinfo \/proc\/self\/mountinfo; then\r\n\texec unshare -m -- "$0" "$@"\r\n\techo "$0 must be run in private namespace."\r\n\texit 1\r\nfi\r\n\t\t\r\ncleanup()\r\n{\r\n\tumount -l $BUILDENGINE\/dev\/pts\r\n\tumount -l $BUILDENGINE\/dev\r\n\tumount -l $BUILDENGINE\/proc\r\n\tumount -l $BUILDENGINE\/sys\r\n\tumount -l $BUILDENGINE\/run\r\n\r\n\tumount -l $BUILDENGINE\/home\/mersdk\/share\t\r\n\tumount -l $BUILDENGINE\/home\/src1\r\n\tumount -l $BUILDENGINE\/etc\/ssh\/authorized_keys\r\n\tumount -l $BUILDENGINE\/host_targets\r\n\tumount -l $BUILDENGINE\/etc\/mersdk\/share\r\n}\r\n\r\ntrap "cleanup > \/dev\/null 2>&1; exit" INT QUIT TERM EXIT\r\n\r\nmount --make-slave "$(df -P "$BUILDENGINE" | tail -1 | awk '{print $NF}')"\r\n\r\nmount --bind \/dev "$BUILDENGINE\/dev"\r\nmount --bind \/dev\/pts "$BUILDENGINE\/dev\/pts"\r\nmount --bind \/proc "$BUILDENGINE\/proc"\r\nmount --bind \/sys "$BUILDENGINE\/sys"\r\nmount --bind \/run "$BUILDENGINE\/run"\r\n\r\nmount --bind "$USERDIR" "$BUILDENGINE\/home\/mersdk\/share"\r\nmount --bind "$USERDIR" "$BUILDENGINE\/home\/src1"\r\nmount --bind "$SDK\/mersdk\/ssh" "$BUILDENGINE\/etc\/ssh\/authorized_keys"\r\nmount --bind "$SDK\/mersdk\/targets" "$BUILDENGINE\/host_targets"\r\nmount --bind "$SDK\/vmshare" "$BUILDENGINE\/etc\/mersdk\/share"\r\n\r\n# Rewrite user id and group id entries to match host system's users\r\nupdateConfigs()\r\n{\r\n\tsed -i -e "s\/$1:x:$2:100000:\/$1:x:$(id -u $USER):$(id -g $USER):\/" "$3\/passwd"\r\n\tsed -i -e "s\/$1:x:100000:\/$1:x:$(id -g $USER):\/" "$3\/group"\r\n\tcp \/etc\/resolv.conf "$3\/"\r\n}\r\n\r\nupdateConfigs mersdk 1001 "$BUILDENGINE\/etc"\r\nupdateConfigs nemo 100000 "$BUILDENGINE\/srv\/mer\/targets\/SailfishOS-armv7hl\/etc"\r\nupdateConfigs nemo 100000 "$BUILDENGINE\/srv\/mer\/targets\/SailfishOS-i486\/etc"\r\n\r\ncat > "$BUILDENGINE\/runmersdkengine.sh" << CONTENT\r\n#!\/bin\/bash\r\n\r\ncleanup()\r\n{\r\n\tpkill -KILL -f "\/usr\/bin\/ruby \/usr\/bin\/puma -p 8080 -t 1:1 -e production"\r\n}\r\ntrap "cleanup; exit" INT QUIT TERM EXIT\r\n\r\n# Fix up permissions to point to new uid\/gid of mersdk\r\nmkdir -p \/home\/deploy\/installroot\r\nchown -R mersdk.mersdk \/home\/deploy\/installroot\r\nchown -R mersdk.mersdk \/srv\/mer\/targets\/*\r\nfind \/home\/mersdk | grep -v "\/home\/mersdk\/share" | xargs chown mersdk.mersdk\r\n\r\n# Run web server of build engine as mersdk in background:\r\nsu mersdk -c "cd \/usr\/lib\/sdk-webapp-bundle; \/usr\/bin\/ruby \/usr\/bin\/puma -p 8080 -t 1:1 -e production" &\r\n\r\n# Run SSH Server of build engine as root:\r\n\/usr\/sbin\/sshd -p 2222 -D -e -f \/etc\/ssh\/sshd_config_engine\r\nCONTENT\r\n\r\nchroot "$BUILDENGINE" sh \/runmersdkengine.sh \r\n<\/pre>\n
Don’t forget to <\/p>\n
\r\nchmod 755 \/opt\/run-sailfishos-buildengine.sh\r\n<\/pre>\n
Now exit the root shell and run:<\/p>\n
\r\nsudo \/opt\/run-sailfishos-buildengine.sh\r\n<\/pre>\n
This will start the Open SSH server and the build engine’s web server which is used in the modified Qt Creator of the SailfishOS SDK.
\nPress CTRL+C to terminate the engine at any time.<\/p>\n
Qt Creator will complain that the VM is not started and offers to start the VM for you. Just click No and ignore it. The build is already running in the background.<\/p>\n
Enjoy your fast builds!<\/p>\n","protected":false},"excerpt":{"rendered":"
I have been struggling with the SailfishOS Build Engine VM for quite some time. 4 out of 5 SailfishOS builds of QuasarMX would fail because the Shared Folder (vboxsf) mechanism in VirtualBox at some point starts to corrupt files on my system, even though the system’s RAM and storage are perfectly fine. Since QuasarMX heavily […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-672","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/katastrophos.net\/andre\/blog\/wp-json\/wp\/v2\/posts\/672"}],"collection":[{"href":"https:\/\/katastrophos.net\/andre\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/katastrophos.net\/andre\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/katastrophos.net\/andre\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/katastrophos.net\/andre\/blog\/wp-json\/wp\/v2\/comments?post=672"}],"version-history":[{"count":32,"href":"https:\/\/katastrophos.net\/andre\/blog\/wp-json\/wp\/v2\/posts\/672\/revisions"}],"predecessor-version":[{"id":686,"href":"https:\/\/katastrophos.net\/andre\/blog\/wp-json\/wp\/v2\/posts\/672\/revisions\/686"}],"wp:attachment":[{"href":"https:\/\/katastrophos.net\/andre\/blog\/wp-json\/wp\/v2\/media?parent=672"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/katastrophos.net\/andre\/blog\/wp-json\/wp\/v2\/categories?post=672"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/katastrophos.net\/andre\/blog\/wp-json\/wp\/v2\/tags?post=672"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}