Live-Build lb build “chroot: failed to run command ‘/usr/bin/env’: No such file or directory”Ubuntu...
How can a school be getting an epidemic of whooping cough if most of the students are vaccinated?
If I delete my router's history can my ISP still provide it to my parents?
Cat is tipping over bed-side lamps during the night
Why is Agricola named as such?
Why did Democrats in the Senate oppose the Born-Alive Abortion Survivors Protection Act (2019 S.130)?
When can a QA tester start his job?
Removing disk while game is suspended
A curious equality of integrals involving the prime counting function?
Cookies - Should the toggles be on?
Move fast ...... Or you will lose
Aligning symbols underneath each other neatly
Increasing the flow in descriptions of a sequence of events
Play Zip, Zap, Zop
Why don't hotels mount air conditioning units outside the rooms?
What sets the resolution of an analog resistive sensor?
False written accusations not made public - is there law to cover this?
What is the purpose of easy combat scenarios that don't need resource expenditure?
How can my powered armor quickly replace its ceramic plates?
Increment each digit in a number to form a new number
What is a good reason for every spaceship to carry a weapon on board?
Why am I able to open Wireshark in macOS without root privileges?
Why wasn't TEventArgs made contravariant in the standard event pattern in the .NET ecosystem?
Can you tell from a blurry photo if focus was too close or too far?
Do authors have to be politically correct in article-writing?
Live-Build lb build “chroot: failed to run command ‘/usr/bin/env’: No such file or directory”
Ubuntu chroot “No such file or directory”Is there a proper way to set up a copy-on-write based build env that use your live / as base files?Installing Apache Cordova, unable to locate packageTerminal crashes when running lsblk -h'/bin/bash': no such file or Directory“No such file or directory” after chmodDeleted my /usr/ directory, recovered with chroot now getting a Segmentation fault (core dumped) trying to run SudoUsing “make” command not workingchroot: failed to run command ‘/bin/bash’: No such file or directoryUbuntu won't boot after a power-cut during upgrade
I have a problem with live build
$ sudo lb build --interactive shell
returns with
chroot: failed to run command ‘/usr/bin/env’: No such file or directory
does anyone know what is happening?
command-line chroot
add a comment |
I have a problem with live build
$ sudo lb build --interactive shell
returns with
chroot: failed to run command ‘/usr/bin/env’: No such file or directory
does anyone know what is happening?
command-line chroot
add a comment |
I have a problem with live build
$ sudo lb build --interactive shell
returns with
chroot: failed to run command ‘/usr/bin/env’: No such file or directory
does anyone know what is happening?
command-line chroot
I have a problem with live build
$ sudo lb build --interactive shell
returns with
chroot: failed to run command ‘/usr/bin/env’: No such file or directory
does anyone know what is happening?
command-line chroot
command-line chroot
edited Dec 12 '15 at 11:58
Hayden
asked Dec 12 '15 at 0:47
HaydenHayden
3116
3116
add a comment |
add a comment |
3 Answers
3
active
oldest
votes
I had the same thing happen to me and I think it's because my working directory is mounted from my host OS (mac osx) via vagrant.
P: If the following stage fails, the most likely cause of the problem is with your mirror configuration or a caching proxy.
P: Running debootstrap...
mknod: ‘/vagrant/tutorial1/chroot/test-dev-null’: Operation not permitted
E: Cannot install into target '/vagrant/tutorial1/chroot' mounted with noexec or nodev
P: Begin unmounting filesystems...
P: Saving caches...
chroot: failed to run command ‘/usr/bin/env’: No such file or directory
The '/usr/bin/env': No such file or directory error is because debootstrap failed, and I'd bet the command being run is something along the lines of: chroot /vagrant/tutorial1/chroot /usr/bin/env FOO=bar baz, and chroot is failing to find /usr/bin/env
I moved outside of the /vagrant path on my machine and it seems to be working.
Try looking at earlier messages in the output for clues. Feel free to paste more of the output in here if you are still not certain!
This was, indeed, the source of this problem for me! Weirdly-specific, and probably the first time a “1-point” user has ever helped me in years-upon-years of Stack Exchange use 🤣 — thank you!
– ELLIOTTCABLE
Feb 13 '17 at 3:32
add a comment |
@kitchen's diagnosis of what the error message means is accurate, but the scenario did not match mine. I found ./chroot/debootstrap/debootstrap.log contains additional information about why the debootstrap command is dying:
dpkg-deb: error: archive './/var/cache/apt/archives/base-files_10.1ubuntu2_arm64.deb'
has premature member 'control.tar.xz' before 'control.tar.gz',
giving up
It turns out that the dpkg package was outdated. Upgrading it with apt-get install -y dpkg fixed this bug.
add a comment |
Change Your mirror
As You say lb build stop after
`Chroot not able to run /bin/bash/env no file or director`
This happened Due to , All packages which you set in includ.chroot.packages or whatever
Is not all Dowbloaded
So system Unmounted At that point , Now chroot not do anything even taking Telescope:))
`chnage mirror in lb config , Use stable Mirror
This also happened with me During building Amzux , I try all way , At last i see
Change mieeor && Happy live building:))
New contributor
amzker pro hacker is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f708659%2flive-build-lb-build-chroot-failed-to-run-command-usr-bin-env-no-such-file%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
I had the same thing happen to me and I think it's because my working directory is mounted from my host OS (mac osx) via vagrant.
P: If the following stage fails, the most likely cause of the problem is with your mirror configuration or a caching proxy.
P: Running debootstrap...
mknod: ‘/vagrant/tutorial1/chroot/test-dev-null’: Operation not permitted
E: Cannot install into target '/vagrant/tutorial1/chroot' mounted with noexec or nodev
P: Begin unmounting filesystems...
P: Saving caches...
chroot: failed to run command ‘/usr/bin/env’: No such file or directory
The '/usr/bin/env': No such file or directory error is because debootstrap failed, and I'd bet the command being run is something along the lines of: chroot /vagrant/tutorial1/chroot /usr/bin/env FOO=bar baz, and chroot is failing to find /usr/bin/env
I moved outside of the /vagrant path on my machine and it seems to be working.
Try looking at earlier messages in the output for clues. Feel free to paste more of the output in here if you are still not certain!
This was, indeed, the source of this problem for me! Weirdly-specific, and probably the first time a “1-point” user has ever helped me in years-upon-years of Stack Exchange use 🤣 — thank you!
– ELLIOTTCABLE
Feb 13 '17 at 3:32
add a comment |
I had the same thing happen to me and I think it's because my working directory is mounted from my host OS (mac osx) via vagrant.
P: If the following stage fails, the most likely cause of the problem is with your mirror configuration or a caching proxy.
P: Running debootstrap...
mknod: ‘/vagrant/tutorial1/chroot/test-dev-null’: Operation not permitted
E: Cannot install into target '/vagrant/tutorial1/chroot' mounted with noexec or nodev
P: Begin unmounting filesystems...
P: Saving caches...
chroot: failed to run command ‘/usr/bin/env’: No such file or directory
The '/usr/bin/env': No such file or directory error is because debootstrap failed, and I'd bet the command being run is something along the lines of: chroot /vagrant/tutorial1/chroot /usr/bin/env FOO=bar baz, and chroot is failing to find /usr/bin/env
I moved outside of the /vagrant path on my machine and it seems to be working.
Try looking at earlier messages in the output for clues. Feel free to paste more of the output in here if you are still not certain!
This was, indeed, the source of this problem for me! Weirdly-specific, and probably the first time a “1-point” user has ever helped me in years-upon-years of Stack Exchange use 🤣 — thank you!
– ELLIOTTCABLE
Feb 13 '17 at 3:32
add a comment |
I had the same thing happen to me and I think it's because my working directory is mounted from my host OS (mac osx) via vagrant.
P: If the following stage fails, the most likely cause of the problem is with your mirror configuration or a caching proxy.
P: Running debootstrap...
mknod: ‘/vagrant/tutorial1/chroot/test-dev-null’: Operation not permitted
E: Cannot install into target '/vagrant/tutorial1/chroot' mounted with noexec or nodev
P: Begin unmounting filesystems...
P: Saving caches...
chroot: failed to run command ‘/usr/bin/env’: No such file or directory
The '/usr/bin/env': No such file or directory error is because debootstrap failed, and I'd bet the command being run is something along the lines of: chroot /vagrant/tutorial1/chroot /usr/bin/env FOO=bar baz, and chroot is failing to find /usr/bin/env
I moved outside of the /vagrant path on my machine and it seems to be working.
Try looking at earlier messages in the output for clues. Feel free to paste more of the output in here if you are still not certain!
I had the same thing happen to me and I think it's because my working directory is mounted from my host OS (mac osx) via vagrant.
P: If the following stage fails, the most likely cause of the problem is with your mirror configuration or a caching proxy.
P: Running debootstrap...
mknod: ‘/vagrant/tutorial1/chroot/test-dev-null’: Operation not permitted
E: Cannot install into target '/vagrant/tutorial1/chroot' mounted with noexec or nodev
P: Begin unmounting filesystems...
P: Saving caches...
chroot: failed to run command ‘/usr/bin/env’: No such file or directory
The '/usr/bin/env': No such file or directory error is because debootstrap failed, and I'd bet the command being run is something along the lines of: chroot /vagrant/tutorial1/chroot /usr/bin/env FOO=bar baz, and chroot is failing to find /usr/bin/env
I moved outside of the /vagrant path on my machine and it seems to be working.
Try looking at earlier messages in the output for clues. Feel free to paste more of the output in here if you are still not certain!
answered Dec 17 '15 at 7:49
kitchenkitchen
311
311
This was, indeed, the source of this problem for me! Weirdly-specific, and probably the first time a “1-point” user has ever helped me in years-upon-years of Stack Exchange use 🤣 — thank you!
– ELLIOTTCABLE
Feb 13 '17 at 3:32
add a comment |
This was, indeed, the source of this problem for me! Weirdly-specific, and probably the first time a “1-point” user has ever helped me in years-upon-years of Stack Exchange use 🤣 — thank you!
– ELLIOTTCABLE
Feb 13 '17 at 3:32
This was, indeed, the source of this problem for me! Weirdly-specific, and probably the first time a “1-point” user has ever helped me in years-upon-years of Stack Exchange use 🤣 — thank you!
– ELLIOTTCABLE
Feb 13 '17 at 3:32
This was, indeed, the source of this problem for me! Weirdly-specific, and probably the first time a “1-point” user has ever helped me in years-upon-years of Stack Exchange use 🤣 — thank you!
– ELLIOTTCABLE
Feb 13 '17 at 3:32
add a comment |
@kitchen's diagnosis of what the error message means is accurate, but the scenario did not match mine. I found ./chroot/debootstrap/debootstrap.log contains additional information about why the debootstrap command is dying:
dpkg-deb: error: archive './/var/cache/apt/archives/base-files_10.1ubuntu2_arm64.deb'
has premature member 'control.tar.xz' before 'control.tar.gz',
giving up
It turns out that the dpkg package was outdated. Upgrading it with apt-get install -y dpkg fixed this bug.
add a comment |
@kitchen's diagnosis of what the error message means is accurate, but the scenario did not match mine. I found ./chroot/debootstrap/debootstrap.log contains additional information about why the debootstrap command is dying:
dpkg-deb: error: archive './/var/cache/apt/archives/base-files_10.1ubuntu2_arm64.deb'
has premature member 'control.tar.xz' before 'control.tar.gz',
giving up
It turns out that the dpkg package was outdated. Upgrading it with apt-get install -y dpkg fixed this bug.
add a comment |
@kitchen's diagnosis of what the error message means is accurate, but the scenario did not match mine. I found ./chroot/debootstrap/debootstrap.log contains additional information about why the debootstrap command is dying:
dpkg-deb: error: archive './/var/cache/apt/archives/base-files_10.1ubuntu2_arm64.deb'
has premature member 'control.tar.xz' before 'control.tar.gz',
giving up
It turns out that the dpkg package was outdated. Upgrading it with apt-get install -y dpkg fixed this bug.
@kitchen's diagnosis of what the error message means is accurate, but the scenario did not match mine. I found ./chroot/debootstrap/debootstrap.log contains additional information about why the debootstrap command is dying:
dpkg-deb: error: archive './/var/cache/apt/archives/base-files_10.1ubuntu2_arm64.deb'
has premature member 'control.tar.xz' before 'control.tar.gz',
giving up
It turns out that the dpkg package was outdated. Upgrading it with apt-get install -y dpkg fixed this bug.
answered Jan 16 at 23:41
rgovrgov
1084
1084
add a comment |
add a comment |
Change Your mirror
As You say lb build stop after
`Chroot not able to run /bin/bash/env no file or director`
This happened Due to , All packages which you set in includ.chroot.packages or whatever
Is not all Dowbloaded
So system Unmounted At that point , Now chroot not do anything even taking Telescope:))
`chnage mirror in lb config , Use stable Mirror
This also happened with me During building Amzux , I try all way , At last i see
Change mieeor && Happy live building:))
New contributor
amzker pro hacker is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Change Your mirror
As You say lb build stop after
`Chroot not able to run /bin/bash/env no file or director`
This happened Due to , All packages which you set in includ.chroot.packages or whatever
Is not all Dowbloaded
So system Unmounted At that point , Now chroot not do anything even taking Telescope:))
`chnage mirror in lb config , Use stable Mirror
This also happened with me During building Amzux , I try all way , At last i see
Change mieeor && Happy live building:))
New contributor
amzker pro hacker is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Change Your mirror
As You say lb build stop after
`Chroot not able to run /bin/bash/env no file or director`
This happened Due to , All packages which you set in includ.chroot.packages or whatever
Is not all Dowbloaded
So system Unmounted At that point , Now chroot not do anything even taking Telescope:))
`chnage mirror in lb config , Use stable Mirror
This also happened with me During building Amzux , I try all way , At last i see
Change mieeor && Happy live building:))
New contributor
amzker pro hacker is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Change Your mirror
As You say lb build stop after
`Chroot not able to run /bin/bash/env no file or director`
This happened Due to , All packages which you set in includ.chroot.packages or whatever
Is not all Dowbloaded
So system Unmounted At that point , Now chroot not do anything even taking Telescope:))
`chnage mirror in lb config , Use stable Mirror
This also happened with me During building Amzux , I try all way , At last i see
Change mieeor && Happy live building:))
New contributor
amzker pro hacker is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
amzker pro hacker is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 6 mins ago
amzker pro hackeramzker pro hacker
1
1
New contributor
amzker pro hacker is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
amzker pro hacker is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
amzker pro hacker is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f708659%2flive-build-lb-build-chroot-failed-to-run-command-usr-bin-env-no-such-file%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown