Jump to content

building behind a proxy


Recommended Posts

In theory:

 

here

https://github.com/igorpecovnik/lib/blob/second/deboostrap.sh#L87

 

add:

http_proxy=http://proxy.host:port/

before deboostrap

http://unix.stackexchange.com/questions/38993/global-cache-config-of-debootstrap

 

Please report if it works, than we can add this as option.

Edited by Igor
option
Link to comment
Share on other sites

it happens quite often that the deboostrap-process jumps almost immediatly from 0% to 100%. in this case i get an error when stuff should be compiled in chroot-environment. (eg /bin/sh: 1: arm-linux-gnueabihf-gcc: not found)

 

this also happens on machines without proxy. Any idea? (reboot doesn't help at all, deleting of /source and /output is no help either)

 

florian

Link to comment
Share on other sites

Hello Igor,

 

adding
 

http_proxy=http://proxy.host:port/

before deboostrap

 

 

worked like a charm, but i also had to copy a file (/etc/apt/apt.conf) into my rootfs to make the apt-get within the chroot-environment work. It contains the proxy-settings for apt-get.

 

i realized what happens at the beginning of the process (see my last post). Its not the debootstrap, its the installation of host dependencies which fails without further notice. I couldn't install the gpg-key for aptly. after installing aptly manually everything worked fine with the proxy.

 

Additionally i ran into problems with the size of the sdcard-image. I had to set the size to 8000MB as i got "out of space"-messages when installing the pakets into the sdcard image. (even 6000MB were not enough for trusty with desktop).

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines