Using https_proxy and http_proxy on a System That Has Installed Zones

This section discusses how to set proxies for a system on an internal subnet that does not have a direct connection to the IPS publisher repository. The system uses an http_proxy configuration to connect.

For example, assume that the software on a system running solaris non-global zones is being managed by IPS, using the proxy configuration https_proxy=http://129.156.243.243:3128. The 129.156.243.243:3128 https proxy is configured on port 3128 of a system with the IP address 129.156.243.243. A host name that is resolvable can also be used.

1. Using this example, type the following line to set the proxy in the ksh for the global zone, to allow pkg commands to talk to the publisher over the https proxy.

   # export https_proxy=http://129.156.243.243:3128

2. To allow the solaris zones on the system to use the configured system publishers, run the following command:

   # svccfg -s svc:/application/pkg/system-repository:default setprop config/http_proxy=astring: "https://129.156.243.243:3128"

3. To make the change take effect in the live SMF repository, run:

   # svcadm refresh svc:/application/pkg/system-repository:default setprop

4. To confirm that the setting is operational, run:

   # svcprop svc:/application/pkg/system-repository:default|grep https_proxy

This process allows the solaris zones to contact the publisher set in the global zone as well. Recursive pkg operations into the solaris branded zones will succeed.