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

Build script fails: Operation not permitted #4

Open
omartijn opened this issue Apr 27, 2019 · 3 comments
Open

Build script fails: Operation not permitted #4

omartijn opened this issue Apr 27, 2019 · 3 comments

Comments

@omartijn
Copy link

Trying to execute the build script I get the following:

Using tarball [http://releases.sailfishos.org/sdk/latest/Jolla-latest-Sailfish_SDK_Tooling-i486.tar.bz2]
Downloading 'Jolla-latest-Sailfish_SDK_Tooling-i486.tar.bz2'
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  223M  100  223M    0     0  9595k      0  0:00:23  0:00:23 --:--:-- 9571k
INFO: md5sum matches - download ok
Unpacking tooling ...
Initializing machine ID for tooling 'SailfishOS-latest'
unshare: unshare failed: Operation not permitted
unshare: unshare failed: Operation not permitted
unshare: unshare failed: Operation not permitted
The command '/bin/sh -c sdk-assistant -y create SailfishOS-latest     http://releases.sailfishos.org/sdk/latest/Jolla-latest-Sailfish_SDK_Tooling-i486.tar.bz2' returned a non-zero code: 1

Perhaps it's due to the recent update of the sailfish sdk. i'd really like to use this container, I want to be able to fix/build existing sailfish packages (like Quickddit which now fails to play youtube videos after google mucked something up again), but I can't just build those packages with the SDK, which I'd rather not install.

@SfietKonstantin
Copy link
Owner

I'm working on it :)

@SfietKonstantin
Copy link
Owner

Can you try again with the latest readme / scripts ?

@omartijn
Copy link
Author

Looking at the latest README, I see that build.sh now expects to be run as root. When I run it as a regular user it fails because it tries to add users to the sudoers file.

I don't really understand the idea behind this. Isn't the idea behind using docker that you don't need this? If everything is installed in the docker container it should work just fine, right?

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

No branches or pull requests

2 participants