On Wed, 2010-01-20 at 14:09 -0600, Will Fiveash wrote:
> On Tue, Jan 19, 2010 at 05:43:02PM -0600, Shawn Walker wrote:
> >  On 01/19/10 03:23 PM, Will Fiveash wrote:
> > > I've installed this package in my global zone (running snv_129):
> > >
> > > pkg://contrib.opensolaris.org/[email protected],5.11-0.101:20081209T222607Z
> > >
> > > I want the same package installed in a non-global zone that does not
> > > have external network access.  I tried:
> > >
> > > # zoneadm -z zone1 detach
> > > # zoneadm -z zone1 attach -u
> > > Log File: /var/tmp/kdc-clone.attach_log.QWay_f
> > > Attaching...
> > >
> > >         Global zone version: [email protected],5.11-0.129:20091205T134302Z
> > >     Non-Global zone version: [email protected],5.11-0.129:20091205T134302Z
> > >                  Evaluation: Packages in kdc-clone are in sync with 
> > > global 
> > > zone.
> > > Attach complete.
> > >
> > > But pkg list in zone1 does not show the opensc package installed.  How
> > > do I get this installed?
> > 
> >  The text here is misleading I believe.  I don't think that its intended 
> > that 
> >  it synchronises all packages between your global and non-global zones.   
> >  Instead, I believe it is simply keeping the base OS constraints in-sync 
> >  (based on the "entire" incorporation package).
> > 
> >  If you want to install packages in that zone, then login to the zone and 
> > use 
> >  pkg install <pkg_name>.
> 
> Just tried that, here's what I see:
> 
> # pkg install opensc    
> /usr/lib/python2.6/vendor-packages/pkg/client/api_errors.py:295: 
> DeprecationWarning: BaseException.message has been deprecated as of Python 2.6
>   self.message = message
> pkg: 0/1 catalogs successfully updated:
>    
> Unable to contact valid package server
> Encountered the following error(s):
> Unable to contact any configured publishers. This is likely a network 
> configuration problem.
> /usr/bin/pkg:2014: DeprecationWarning: BaseException.message has been 
> deprecated as of Python 2.6
>   if cre.message:
> 
> Note, the non-global zones do not have SWAN access.  What does one do in
> this case?

Hi Will.

I suspect there's a (big) difference between what one *should* do versus
what one *can* do. I've been hoping someone here will respond to your
question with an answer to the former so that I can stop doing the
latter. :-) Since that has yet to transpire....

Given non-global zone foo whose zonepath is /export/zones/foo, I am able
to install packages into it from within the global zone via:

    # pkg -R /export/zones/foo/root install SUNWmy-pkg

Looking at your output (i.e. pkg: 0/1 catalogs successfully updated), I
assume you'll first need to add Contrib as a publisher in your
non-global zone.
    
(Disclaimer: I tend to learn by breaking things and then recovering.
Observation: When I propose something which is unsound, it's not long
before someone here points out where I've gone wrong. ;-) )
    
Take care.
--joanie

_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss

Reply via email to