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

vagga::wrapper: Error executing _build: Could not run versioner #508

Open
KarelWintersky opened this issue Dec 12, 2018 · 2 comments
Open

Comments

@KarelWintersky
Copy link
Contributor

KarelWintersky commented Dec 12, 2018

vagga::wrapper: Error executing _build: Could not run versioner: error when executing: No such file or directory (os error 2)

→ vagga run
ERROR 2018-12-12T22:37:57Z: vagga::wrapper: Error executing _build: Could not run versioner: error when executing: No such file or directory (os error 2)
Command <Command "/proc/self/exe" "__wrapper__" "_build" "mysql-dev"; environ[3]; uid_map=[UidMap { inside_uid: 0, outside_uid: 1000, count: 1 }, UidMap { inside_uid: 1, outside_uid: 100000, count: 65535 }]; gid_map=[GidMap { inside_gid: 0, outside_gid: 1000, count: 1 }, GidMap { inside_gid: 1, outside_gid: 100000, count: 65535 }]> exited with code 124

My system:

# uname -a

Linux blacktower 4.14.65-gentoo #3 SMP Tue Dec 4 03:15:09 MSK 2018 x86_64 Intel(R) Celeron(R) CPU N3150 @ 1.60GHz GenuineIntel GNU/Linux

# zcat /proc/config.gz  | grep CONFIG_USER_NS
CONFIG_USER_NS=y

Vagga compiled from source using RUST docker image ( https://github.com/tailhook/vagga/blob/master/docs/installation.rst#building-from-source-using-docker )

@KarelWintersky KarelWintersky changed the title vagga::wrapper: Error executing _build: Could not run versioner: error when executing: No such file or directory (os error 2) vagga::wrapper: Error executing _build: Could not run versioner Dec 12, 2018
@KarelWintersky
Copy link
Contributor Author

KarelWintersky commented Dec 12, 2018

I added option key --target=x86_64-unknown-linux-mus as recommended here: #6 (comment)

so, commandline is:

docker run --rm --user "$(id -u)":"$(id -g)" -e VAGGA_VERSION=v0.8.1-24-g1afd5a0 -v "$PWD":/usr/src/vagga -w /usr/src/vagga rust cargo build --release --target=x86_64-unknown-linux-musl

Result:

....
  Downloaded unicode-normalization v0.1.7
   Compiling proc-macro2 v0.4.20
   Compiling version_check v0.1.5
   Compiling build_const v0.2.1
   Compiling typenum v1.10.0
   Compiling unicode-xid v0.1.0
   Compiling libc v0.2.43
error[E0463]: can't find crate for `std`
  |
  = note: the `x86_64-unknown-linux-musl` target may not be installed

error: aborting due to previous error

For more information about this error, try `rustc --explain E0463`.
error: Could not compile `libc`.
warning: build failed, waiting for other jobs to finish...
error: build failed

@KarelWintersky
Copy link
Contributor Author

KarelWintersky commented Dec 12, 2018

As recommended, I run:

→ docker run --rm --user "$(id -u)":"$(id -g)" -e VAGGA_VERSION=v0.8.1-24-g1afd5a0 -v "$PWD":/usr/src/vagga -w /usr/src/vagga rust rustc --explain E0463
A plugin/crate was declared but cannot be found. Erroneous code example:


> #![feature(plugin)]
> #![plugin(cookie_monster)] // error: can't find crate for `cookie_monster`
> extern crate cake_is_a_lie; // error: can't find crate for `cake_is_a_lie`


You need to link your code to the relevant crate in order to be able to use it
(through Cargo or the `-L` option of rustc example). Plugins are crates as
well, and you link to them the same way.

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

1 participant