| commit | 4b5603eaa3b690f621835f23427e69ba8de8fd40 | [log] [tgz] |
|---|---|---|
| author | azvyagintsev <azvyagintsev@mirantis.com> | Fri Sep 14 16:33:14 2018 +0300 |
| committer | azvyagintsev <azvyagintsev@mirantis.com> | Fri Sep 14 21:46:04 2018 +0300 |
| tree | 7d15faf349c5201aac47121d472bd082dabe5a0f | |
| parent | 41a6b8231579bad2aa9f9592a7f34241b561e9a7 [diff] |
Fix libsodium downgrade issue
* For some reason, apt going to be crazy
if found identical pkgs in different repos:
apt-cache policy libsodium18
libsodium18:
Installed: 1.0.8-5
Candidate: 1.0.8-5
Version table:
*** 1.0.8-5 500
500 http://mirror.mirantis.com/proposed/ubuntu xenial/universe amd64 Packages
100 /var/lib/dpkg/status
1.0.8-5 500
500 https://mirror.mirantis.com/testing/saltstack-2017.7/xenial xenial/main amd64 Packages
So, lets pin it from the began to _one_ repo
* Misc: switch to always use staric bootstrap.saltstack.com.sh
remove non-relevant anymore AllowUnauthenticated
Closes-Bug: PROD-22326 (PROD:22326)
Change-Id: Ib9f7cdd1bcfb1451b1e17dfcdacadace249cccc3
Packer templates are used to:
PACKER_URL="https://dl.bintray.com/mitchellh/packer/packer_0.8.2_linux_amd64.zip" PACKER_ZIP=$(basename ${PACKER_URL}) PACKER_ZIP_MD5="bc37abe5e183a11bd8c1b2efc385059b" mkdir -p ~/bin/packer cd ~/bin/packer export PATH="${PATH}:~/bin/packer" wget -O ${PACKER_ZIP} ${PACKER_URL} echo "${PACKER_ZIP_MD5} ${PACKER_ZIP}" >> md5sum md5sum -c --status md5sum unzip ${PACKER_ZIP}
Enter build directory by selecting OS type and version. You should see file template.json.
Start building some images:
packer build -only=virtualbox-iso template.json
Directory http/ contains OS installer config files (preseed/kickstart/..)
Directory scripts/ contains set of scripts for provision after image build.