|
Hi Cole, This is an interesting error, if you run: virt-bootstrap
docker://fedora /tmp/foo virt-bootstrap will check if the path "/tmp/foo" exists and
will create in case it does not. Then it should work except if
the path "/tmp/foo" exists and is not owned by another user
(root) even though with permissions 755. In such case you will get "Permission denied". (I'm not sure
why, though.) Steps to reproduce: $ sudo mkdir /tmp/foo $ sudo chmod 755 /tmp/foo $ ls -al /tmp/test5 $ touch /tmp/foo/test On 27/06/17 16:50, Cole Robinson wrote:
On 06/23/2017 02:49 PM, Radostin wrote:Hi Cole, Thank you for the feedback. To solve the problem with virt-bootstrap/skopeo use: virt-bootstrap docker://fedora /tmp/fooThanks, indeed that works. Guess I'm just used to the libvirt qemu:///system URI :) Trying it now with docker://fedora ... does virt-bootstrap require running as root? It doesn't seem to generate a usable container dir without root, I see errors like: /bin/tar: etc/alternatives/cifs-idmap-plugin: Cannot open: Permission denied /bin/tar: etc/alternatives/libnssckbi.so.x86_64: Cannot open: Permission denied /bin/tar: etc/cifs-utils/idmap-plugin: Cannot open: Permission denied /bin/tar: etc/crypto-policies/back-ends/bind.config: Cannot open: Permission denied /bin/tar: etc/crypto-policies/back-ends/gnutls.config: Cannot open: Permission denied /bin/tar: etc/crypto-policies/back-ends/gnutls28.config: Cannot open: Permission denied /bin/tar: etc/crypto-policies/back-ends/java.config: Cannot open: Permission denied /bin And so on. But virt-bootstrap still reports success. Another issue I noticed: would be nice to get the virt-bootstrap output into the virt-manager debug log The UI generally looks good though, nice work - Cole |
_______________________________________________ virt-tools-list mailing list virt-tools-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/virt-tools-list
