Page Comparison

Thanks to Gary Wu for setting up the original proxies and providing the source material for the description below.

The infrastucture provides an APT and DOCKER proxy to reduce bandwidth utilization for installs in the Intel/Windriver Lab.

...

1. apt-get update

2. apt-get -y install squid-deb-proxy

   1. this will install and start the apt proxy on port 8000

3. If you need to re-create the Volume mount for the docker registry
   • Create your instance (Openstack UI)
   • Create your volume (Openstack UI)
   • Attach volume to instance (Openstack UI)

4. After creating the volume or to re-use the existing volume, go into the nexus-proxy instance:
   1. lsblk -f # identify the new volume device, probably /dev/vdb
   2. cgdisk /dev/vdb # create your partition as /dev/vdb1
   3. mkfs.ext4 L docker proxy /dev/vdb1 to create the FS on /dev/vdb1
      
      1. Original command: mkfs.xfs -f -L docker-proxy /dev/vdb1 # create xfs FS on /dev/vdb1
      ; you can use ext4 if you like
      2. the current windriver proxy uses ext4 so that is why we should that in the fstab config
   4. mkdir -p /mnt/registry # create mount for FS
   5. add something like the following to your /etc/fstab, with your own FS UUID of course
   6. UUID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx /mnt/registry ext4 noatime 0 0

   7. 
      

      Code Block
      title /etc/fstab collapse true
      LABEL=cloudimg-rootfs / ext4 defaults 0 0 LABEL=UEFI /boot/efi vfat defaults 0 0 # vdb ext4 5d493140-c4b7-42f0-9fa1-c9c8d8ac3a0e UUID=5d493140-c4b7-42f0-9fa1-c9c8d8ac3a0e /mnt/registry ext4 noatime 0 0

      
      

   8. mount /mnt/registry/
   9. Reboot to be sure that the FS can be mounted correctly

5. apt-get install docker.io

6. docker run -d -p 5000:5000 --restart=unless-stopped --name registry -v /mnt/registry:/var/lib/registry -e REGISTRY_PROXY_REMOTEURL=https://nexus3.onap.org:10001 registry:2

...