ae74cd056e
Sometimes, trove image builds fail because of package authentication issues. This is often times related to the inability to get to a key server, and not indicative of anything more serious than that. The (strongly discouraged in production use cases) workaround for this is to pass the --allow-unauthenticated option to apt-get install. I say 'Closes-Bug' below but I realize that this is a white lie. What it fixes is only the Trove elements. The image build process uses elements from other places (triple-o, for example). These can still fail for the same reason. There is a much bigger hammer that we can use if we need it, and that is to throw the line 'APT::Get::AllowUnauthenticated "true";' into a conf file in /etc/apt/apt.conf.d/. If this hammer isn't big enough, we can revist later. Change-Id: I009697332bb2a8e1e60b17c10944faed5c311da3 Closes-Bug:#1646856
7 lines
160 B
Bash
Executable File
7 lines
160 B
Bash
Executable File
#!/bin/bash
|
|
# Install baseline packages and tools.
|
|
|
|
set -e
|
|
set -o xtrace
|
|
|
|
apt-get --allow-unauthenticated install -y language-pack-en python-software-properties |