Problems with Debootstrap #5932
Comments
Wrong steps or something is wrong with Ubuntu repositories. At least I don't have access to ARM64 packages, only AMD64 and i386 are available. See below |
Have not read profile due to non-login shell.
Are you sure that PATH is correctly set? Should be |
Yes. added all the necessary paths including. /sbin /usr/local, paths
Whoops. i mean. i used ports.ubuntu.com Repository. and it downloads the arm64 bootstrap packages: I don't exactly remember because there's too many Ubuntu repos. like old-releases, ports, and archive But after downloading packages. it only extracts the packages but didn't go to configuration steps. leaving the /debootstrap directory left behind. and didn't specify the foregin argument so normally it should automatically configure it than performing a debootstrap --second-stage |
|
FYI: Here's the log: Terminal Transcript: debootstrap.log file: |
|
I confirm that I also have the same problems with debootstrap'ed Debian. |
|
Problem is here: Debootstrap shouldn't execute |
|
Does Debootstrap uses |
|
It is patched for and few other places to use proot. |
|
It also has following patch for debian-common chown is not proot'ed: |
|
@wmcb-tech |
|
@xeffyr it does skips the configuration of fstab but the issue is that when symlink has changed. it gives an error with Debian Jessie (armhf) and Ubuntu Trusty:
However i haven't tested this on Android x86 with SELinux disabled. only my phone I was so close. maybe due to the Restrictions of my phone, |
Need to report this to https://github.com/termux/proot, maybe @michalbednarski knows what to do with symbolic link size changes. Will try on my device. |
|
Got failure at this step: |
|
I guess proot is not stable at all on newer devices. but Debootstrap in termux is useful for just Bootstrapping a latest debian system (buster/stretch). |
|
In case of Debootstrap, problem is not with Also I can make Debian rootfs for use with |
|
Thanks @xeffyr this should make termux more useful. |
|
Added just before the package configuration command in Debootstrap files and it seems doesn't work. Binaries are being restored and I still get So variant with getting sane rootfs of Ubuntu or Debian is only |
|
This issue/PR has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
|
issue still relevant. is anyone looking at this? ref #6424 ˋˋˋ returns: ˋˋˋ and checking the log then gives: ˋˋˋ then, excluding dash using --exclude returns: ˋˋˋ checking the new log gives: ˋˋˋ |
ghost
reopened this
|
@xeffyr edited previous with feedback and log (tail -n 5) |
|
@xeffyr new development!!! On a clean Termux setup (0.117/API 0.51) ˋˋˋ the debootstrap process returns as last line: ˋˋˋ The process seems to complete (?) without any errors when the debootstrap directory location is NOT set under Termux's $PREFIX... Perhaps this be due to permission scheme? I have tested incrementally these arguments: --exclude=systemd both run properly and without any error on last line. |
Fails in both $HOME or $PREFIX: |
|
|
|
My fault. It is not possible to reproduce I will delete previous comments regarding that. |
@xeffyr yes, this is what I have come to notice. but not when the root dir is set in the internal storage i.e.: /storage/emulated/0/, hence the $HOME/storage/shared/testing - this is why I asked if it may have had anything to do with overall system permissions? Another thing I've come to notice is that debootstrap does not seem to unpack anything? the only directories present under 'testing' were 'debootstrap' (of course) and 'var'.... Aside from the obvious bits pertaining to architecture and host system, this link makes me think that debootstrap unpacks the base system from the packages that are loaded as well and populates 'testing' with the usual directories? |
@xeffyr Probably you spoke too soon about it. reproducing it with this is probably |
|
Should be fixed in |
In my case I forgot about enabling link2symlink and it failed during |
|
This issue/PR has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
|
Debootstrap appears to be working now (needs binutils though for some distributions). Don't forget to use ports repository for ARM and AArch64 devices, as original is only for x86(64) CPUs. Login to the rootfs:
|
Problem description
Hi. i was using Debootstrap to create a minimal Debian 9/10 system using Termux to create a chroot environment it works fine there's a working apt package manager. but i tried to setup an Ubuntu Trusty and Debian jessie to see if it works. but after setting that up there's no APT package manager and the packages didn't Configure. just extracted
Steps to reproduce
Expected behavior
I was expecting to work just fine to test old programs in bootstrapped environment. just like setting up a Ubuntu 14.04 on my PC using Debootstrap
Additional information
After setting up a trusty base system. i was hoping to work just fine but after logging in. i think the bash shell is unconfigured than debian stable system and instead of
root@localhost~#it saysbash x.x#at PS1 environment variableand by typing apt to update packages. it says
bash: apt: command not foundTried Debian 8 and 7 but it's seems it's the same problem that i was configuring trusty base system
Device Architecture: aarch64
Android Version: 9
Rooted: No
The text was updated successfully, but these errors were encountered: