Hi,
after update to prestable3, all my local zones are reporting pkg: No
image found. for all pkg operations.
Update of zones was done by usual detach/attach -u, this works. Also if
I run pkg -R zone-root command from global zone, it works. But not
in zone itself.
Am I alone?
Best
That sounds like the pkg in the zone didn't get updated, and doesn't
speak the new image format (which the pkg in the GZ updated it to).
-- Rich
___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
Having the same issue after updating global and non-global zones to
oi_151a4. Cant install anything new on the non-global zones.
- Mark
On Fri, May 11, 2012 at 5:13 AM, Milan Jurik milan.ju...@xylab.cz wrote:
Hi,
after update to prestable3, all my local zones are reporting pkg: No image
Hi Rich,
Richard Lowe píše v pá 11. 05. 2012 v 11:17 -0400:
That sounds like the pkg in the zone didn't get updated, and doesn't
speak the new image format (which the pkg in the GZ updated it to).
and you are right:
root@housenka:~# pkg info package/pkg
FMRI:
One possibility:
One of the recent pre-stable updates came with an image format
update, which older pkg won't be able to read
What does that mean? The image format in the global zone, which was updated in
the first place, still works. Is it possible, that the image format in the zone
is
Hi!
After updating my global zone to OI_151a3, I also updated my non global zones
by executing
zoneadm zonename detatch
and
zoneadm zonename attach -u
After that procedure I get the following error on all pkg commands:
pkg: No image found.
Thus I can not update / install any packages
On 29/04/2012, at 4:34 PM, Achim Wolpers achim...@googlemail.com wrote:
Hi!
After updating my global zone to OI_151a3, I also updated my non global zones
by executing
zoneadm zonename detatch
and
zoneadm zonename attach -u
After that procedure I get the following error on all
One possibility:
One of the recent pre-stable updates came with an image format
update, which older pkg won't be able to read
Another possibility:
The same update is umask-sensitive, so if you have a restrictive
umask, /var/pkg will become unreadable (making it 0755 again should
wake things
