Fam Zheng <f...@redhat.com> writes: > On Tue, 03/01 09:52, Alex Bennée wrote: >> >> Fam Zheng <f...@redhat.com> writes: >> >> > On Mon, 02/29 17:18, Alex Bennée wrote: >> >> >> >> Fam Zheng <f...@redhat.com> writes: >> >> >> >> > Signed-off-by: Fam Zheng <f...@redhat.com> >> >> >> >> I think we need to include the dtc libs in here unless we need to ship >> >> all submodules in the tree as well. >> > >> > OK, will take a look. >> > >> >> >> >> Is there a way to get a plain install shell? PAUSE=1 on the test shells >> >> doesn't seem to allow me to install anything. >> > >> > What is the error when you install things? I think it is an unmodified >> > shell >> > and "yum" or "apt-get" should just work. It's just that when the container >> > exits the changes will be discarded. >> >> So running: >> >> make docker-test-quick@ubuntu PAUSE=1 >> >> And I got a shell I wanted to try and get working: >> >> root@72d09615d5b2:/var/tmp/qemu.tmp# ./configure >> >> ERROR: DTC (libfdt) version >= 1.4.0 not present. Your options: >> (1) Preferred: Install the DTC (libfdt) devel package >> (2) Fetch the DTC submodule, using: >> git submodule update --init dtc >> >> root@72d09615d5b2:/var/tmp/qemu.tmp# apt-cache search libfdt >> libfdt-dev - Flat Device Trees manipulation library - development >> files >> libfdt1 - Flat Device Trees manipulation library >> root@72d09615d5b2:/var/tmp/qemu.tmp# apt-get install libfdt-dev >> Reading package lists... Done >> Building dependency tree >> Reading state information... Done >> The following extra packages will be installed: >> libfdt1 >> The following NEW packages will be installed: >> libfdt-dev libfdt1 >> 0 upgraded, 2 newly installed, 0 to remove and 10 not upgraded. >> Need to get 37.8 kB of archives. >> After this operation, 216 kB of additional disk space will be used. >> Do you want to continue? [Y/n] >> Err http://archive.ubuntu.com/ubuntu/ trusty/main libfdt1 amd64 >> 1.4.0+dfsg-1 >> Could not resolve 'archive.ubuntu.com' >> Err http://archive.ubuntu.com/ubuntu/ trusty/main libfdt-dev amd64 >> 1.4.0+dfsg-1 >> Could not resolve 'archive.ubuntu.com' >> E: Failed to fetch >> http://archive.ubuntu.com/ubuntu/pool/main/d/device-tree-compiler/libfdt1_1.4.0+dfsg-1_amd64.deb >> Could not resolve 'archive.ubuntu.com' >> >> E: Failed to fetch >> http://archive.ubuntu.com/ubuntu/pool/main/d/device-tree-compiler/libfdt-dev_1.4.0+dfsg-1_amd64.deb >> Could not resolve 'archive.ubuntu.com' >> >> E: Unable to fetch some archives, maybe run apt-get update or try with >> --fix-missing? >> root@72d09615d5b2:/var/tmp/qemu.tmp# apt-get update >> Err http://archive.ubuntu.com trusty InRelease >> >> Err http://archive.ubuntu.com trusty-updates InRelease >> >> Err http://archive.ubuntu.com trusty-security InRelease >> >> Err http://archive.ubuntu.com trusty Release.gpg >> Could not resolve 'archive.ubuntu.com' >> Err http://archive.ubuntu.com trusty-updates Release.gpg >> Could not resolve 'archive.ubuntu.com' >> Err http://archive.ubuntu.com trusty-security Release.gpg >> Could not resolve 'archive.ubuntu.com' >> Reading package lists... Done >> W: Failed to fetch >> http://archive.ubuntu.com/ubuntu/dists/trusty/InRelease >> >> W: Failed to fetch >> http://archive.ubuntu.com/ubuntu/dists/trusty-updates/InRelease >> >> W: Failed to fetch >> http://archive.ubuntu.com/ubuntu/dists/trusty-security/InRelease >> >> W: Failed to fetch >> http://archive.ubuntu.com/ubuntu/dists/trusty/Release.gpg Could not >> resolve 'archive.ubuntu.com' >> >> W: Failed to fetch >> http://archive.ubuntu.com/ubuntu/dists/trusty-updates/Release.gpg >> Could not resolve 'archive.ubuntu.com' >> >> W: Failed to fetch >> http://archive.ubuntu.com/ubuntu/dists/trusty-security/Release.gpg >> Could not resolve 'archive.ubuntu.com' >> >> W: Some index files failed to download. They have been ignored, or old >> ones used instead. >> >> >> So it looks like networking isn't working in the test images. For >> debugging problems I think we need to be able to install stuff on a >> running image so we can then fix the base recipes. > > Oh yes, I added "-net=none" to the "docker run" command for better isolation. > So in this case we should enable it. Let's rename PAUSE=1 to DEBUG=1 and > enable network.
Sounds good. > > Fam -- Alex Bennée
