[qubes-users] Make one qube accessible on all ip ports to all other qubes
Hi all, I've made a qube with a lot of docker apps in it, and it also stores my local git repository. How do I make it visible to all other qubes? the docker qube and most other qubes are all using sys-firewall. It seems to have to do that there are firewall rules for all qubes, do I have to enable access for each qube individually using the Qubes VM Manager and the VM settings > firewall rules? Thanks, --Opal -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/b03f89d0-8ed6-4b2b-bee0-62c257a5bba6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Building Qubes from source, strange error.
On Saturday, March 25, 2017 at 3:43:37 PM UTC+1, lok...@gmail.com wrote: > On Friday, 24 March 2017 19:34:47 UTC+8, Opal Raava wrote: > > > > Ah, problem solved. In the web build documentation it says to: > > > > > > cp example-configs/qubes-os-master.conf builder.conf > > > > > > if you instead do: > > > > > > cp example-configs/qubes-os-r3.2.conf > > > > > > you get a better branch. I'm currently trying to build that > > > > I have now a new shiny ISO, so this works. Isn't it a bug in the website > > documentation that they recommend building from the master branch? > > I'm building it myself at the moment. I'm wondering if what I'll be getting > is something identical to the release image that you can download? > > My goal with all of this is to build an image that contains the most recent > release in the image, so that I might be able to escape the Catch-22 > situation where I need the network in order to download the update so I can > use the network. The build procedure does not give an identical iso: $ sha256sum ../Qubes-R3.2-x86_64.iso Qubes-DVD-x86_64-20170324.iso 6b998045a513dcdd45c1c6e61ace4f1b4e7eff799f381dccb9eb0170c80f678a ../Qubes-R3.2-x86_64.iso b51b6aa9e468eacf279b6932d4a1b615495ae38fe458b92143be98ddd57c84ac Qubes-DVD-x86_64-20170324.iso -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/a18a0015-cd32-459f-bbdf-1a7de6e7b722%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Building Qubes from source, strange error.
On Thursday, March 23, 2017 at 9:40:57 PM UTC+1, Opal Raava wrote: > On Thursday, March 23, 2017 at 8:23:15 PM UTC+1, Opal Raava wrote: > > On Thursday, March 23, 2017 at 12:11:51 PM UTC+1, Unman wrote: > > > On Thu, Mar 23, 2017 at 03:40:34AM -0700, lokedhs wrote: > > > > On Thursday, 23 March 2017 18:23:30 UTC+8, Opal Raava wrote: > > > > > On Thursday, March 23, 2017 at 3:27:58 AM UTC+1, lok...@gmail.com > > > > > wrote: > > > > > > On Thursday, 23 March 2017 02:45:53 UTC+8, Opal Raava wrote: > > > > > > > > > > > > > Which tells us that we probably really do need version 3.9.0 of > > > > > > > qubes-tools. > > > > > > > > > > > > Where can that version be found? Looking at the latest master of > > > > > > qubes-linux-utils, it only contains version 3.2.3: > > > > > > > > > > > > https://github.com/QubesOS/qubes-linux-utils/blob/master/version > > > > > > > > > Yes, and that is what surprises me as well. The relevant source has > > > > > not been touched in a while. I've looked, but I don't know why the > > > > > build breaks. > > > > > > > > > > All I know for a fact is what you said, it asks for 3.9.0 and > > > > > delivers 3.2.3 at the master branch. And that the relevant source > > > > > files all have not been changed recently. > > > > > > > > The spec file was updated from 2.0.10 to 3.9.0 as of commit > > > > 9780a95a0ad20b63f2da401f108f2dcb3511554b. The interesting thing is that > > > > the commit was on the 17'th December 2015. This is more than half a > > > > year before the most recent ISO images were built. > > > > > > > > I really have no idea what the cause for this could be. > > > > > > > > Regards, > > > > Elias > > > > > > > > > > Finally I understand - you're trying to build a full build of master - > > > I just dont think this works at the moment - you could *try* following > > > my suggestion of NOT building artwork at all - just comment it out. > > > > > > Lots of the devel work on v4 (that's now in master) is in the devs repos > > > - you can see the mysterious 3.9 here: > > > https://github.com/woju/qubes-linux-utils/tree/core3-devel > > > > > > So I think you have to cherry pick from a number of different repos to > > > get something like a working v4 if that's what you want. > > > At least from marmarek and woju. > > > I dont have scope to try this. > > > > > > (You can just build some components as you like - e.g just the manager.) > > > > > > It IS possible to build templates from master, and they seem to work > > > fine with 3.2 :although marek has said that things might break, I haven't > > > seen this as yet.) > > > > > > unman > > > > Ah okay, so all we have to do is specify 'releng3.2' into github or > > something to build the R3.2 branch? > > Ah, problem solved. In the web build documentation it says to: > > cp example-configs/qubes-os-master.conf builder.conf > > if you instead do: > > cp example-configs/qubes-os-r3.2.conf > > you get a better branch. I'm currently trying to build that I have now a new shiny ISO, so this works. Isn't it a bug in the website documentation that they recommend building from the master branch? -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/4e763334-d7fc-49da-8b0b-0f4de7a012b3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Building Qubes from source, strange error.
On Thursday, March 23, 2017 at 8:23:15 PM UTC+1, Opal Raava wrote: > On Thursday, March 23, 2017 at 12:11:51 PM UTC+1, Unman wrote: > > On Thu, Mar 23, 2017 at 03:40:34AM -0700, lokedhs wrote: > > > On Thursday, 23 March 2017 18:23:30 UTC+8, Opal Raava wrote: > > > > On Thursday, March 23, 2017 at 3:27:58 AM UTC+1, lok...@gmail.com wrote: > > > > > On Thursday, 23 March 2017 02:45:53 UTC+8, Opal Raava wrote: > > > > > > > > > > > Which tells us that we probably really do need version 3.9.0 of > > > > > > qubes-tools. > > > > > > > > > > Where can that version be found? Looking at the latest master of > > > > > qubes-linux-utils, it only contains version 3.2.3: > > > > > > > > > > https://github.com/QubesOS/qubes-linux-utils/blob/master/version > > > > > > > Yes, and that is what surprises me as well. The relevant source has not > > > > been touched in a while. I've looked, but I don't know why the build > > > > breaks. > > > > > > > > All I know for a fact is what you said, it asks for 3.9.0 and delivers > > > > 3.2.3 at the master branch. And that the relevant source files all have > > > > not been changed recently. > > > > > > The spec file was updated from 2.0.10 to 3.9.0 as of commit > > > 9780a95a0ad20b63f2da401f108f2dcb3511554b. The interesting thing is that > > > the commit was on the 17'th December 2015. This is more than half a year > > > before the most recent ISO images were built. > > > > > > I really have no idea what the cause for this could be. > > > > > > Regards, > > > Elias > > > > > > > Finally I understand - you're trying to build a full build of master - > > I just dont think this works at the moment - you could *try* following > > my suggestion of NOT building artwork at all - just comment it out. > > > > Lots of the devel work on v4 (that's now in master) is in the devs repos > > - you can see the mysterious 3.9 here: > > https://github.com/woju/qubes-linux-utils/tree/core3-devel > > > > So I think you have to cherry pick from a number of different repos to > > get something like a working v4 if that's what you want. > > At least from marmarek and woju. > > I dont have scope to try this. > > > > (You can just build some components as you like - e.g just the manager.) > > > > It IS possible to build templates from master, and they seem to work > > fine with 3.2 :although marek has said that things might break, I haven't > > seen this as yet.) > > > > unman > > Ah okay, so all we have to do is specify 'releng3.2' into github or something > to build the R3.2 branch? Ah, problem solved. In the web build documentation it says to: cp example-configs/qubes-os-master.conf builder.conf if you instead do: cp example-configs/qubes-os-r3.2.conf you get a better branch. I'm currently trying to build that -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/5152be38-7dfd-492b-ba2b-e6eae6557c57%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Building Qubes from source, strange error.
On Thursday, March 23, 2017 at 12:11:51 PM UTC+1, Unman wrote: > On Thu, Mar 23, 2017 at 03:40:34AM -0700, lokedhs wrote: > > On Thursday, 23 March 2017 18:23:30 UTC+8, Opal Raava wrote: > > > On Thursday, March 23, 2017 at 3:27:58 AM UTC+1, lok...@gmail.com wrote: > > > > On Thursday, 23 March 2017 02:45:53 UTC+8, Opal Raava wrote: > > > > > > > > > Which tells us that we probably really do need version 3.9.0 of > > > > > qubes-tools. > > > > > > > > Where can that version be found? Looking at the latest master of > > > > qubes-linux-utils, it only contains version 3.2.3: > > > > > > > > https://github.com/QubesOS/qubes-linux-utils/blob/master/version > > > > > Yes, and that is what surprises me as well. The relevant source has not > > > been touched in a while. I've looked, but I don't know why the build > > > breaks. > > > > > > All I know for a fact is what you said, it asks for 3.9.0 and delivers > > > 3.2.3 at the master branch. And that the relevant source files all have > > > not been changed recently. > > > > The spec file was updated from 2.0.10 to 3.9.0 as of commit > > 9780a95a0ad20b63f2da401f108f2dcb3511554b. The interesting thing is that the > > commit was on the 17'th December 2015. This is more than half a year before > > the most recent ISO images were built. > > > > I really have no idea what the cause for this could be. > > > > Regards, > > Elias > > > > Finally I understand - you're trying to build a full build of master - > I just dont think this works at the moment - you could *try* following > my suggestion of NOT building artwork at all - just comment it out. > > Lots of the devel work on v4 (that's now in master) is in the devs repos > - you can see the mysterious 3.9 here: > https://github.com/woju/qubes-linux-utils/tree/core3-devel > > So I think you have to cherry pick from a number of different repos to > get something like a working v4 if that's what you want. > At least from marmarek and woju. > I dont have scope to try this. > > (You can just build some components as you like - e.g just the manager.) > > It IS possible to build templates from master, and they seem to work > fine with 3.2 :although marek has said that things might break, I haven't > seen this as yet.) > > unman Ah okay, so all we have to do is specify 'releng3.2' into github or something to build the R3.2 branch? -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/42a95c9e-55a9-4ac7-b5e3-5727f83c7225%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Building Qubes from source, strange error.
On Thursday, March 23, 2017 at 3:27:58 AM UTC+1, lok...@gmail.com wrote: > On Thursday, 23 March 2017 02:45:53 UTC+8, Opal Raava wrote: > > > Ok that build did not work. I'm getting the following error: > > > > ../../bin/mkpadlock.py -s 36 -c 0xcc devices/appvm-red.png > > Traceback (most recent call last): > > File "../../bin/mkpadlock.py", line 25, in > > import qubesimgconverter > > ImportError: No module named qubesimgconverter > > ../Makefile.common:39: recipe for target 'devices/appvm-red.png' failed > > make[2]: *** [devices/appvm-red.png] Error 1 > > make[2]: Leaving directory '/home/user/qubes-src/artwork/icons/36x36' > > Makefile:4: recipe for target 'all' failed > > make[1]: *** [all] Error 1 > > > > Which tells us that we probably really do need version 3.9.0 of qubes-tools. > > Where can that version be found? Looking at the latest master of > qubes-linux-utils, it only contains version 3.2.3: > > https://github.com/QubesOS/qubes-linux-utils/blob/master/version > > Regards, > Elias Yes, and that is what surprises me as well. The relevant source has not been touched in a while. I've looked, but I don't know why the build breaks. All I know for a fact is what you said, it asks for 3.9.0 and delivers 3.2.3 at the master branch. And that the relevant source files all have not been changed recently. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/d2ca4d3c-e12c-47ee-b540-7324b734bcea%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Building Qubes from source, strange error.
On Wednesday, March 22, 2017 at 6:47:48 PM UTC+1, Opal Raava wrote: > On Wednesday, March 22, 2017 at 6:45:12 PM UTC+1, Opal Raava wrote: > > On Wednesday, March 22, 2017 at 12:01:53 PM UTC+1, lok...@gmail.com wrote: > > > I'm trying to build Qubes from source, but when following the > > > instructions (https://www.qubes-os.org/doc/qubes-builder/), the build > > > fails with the message below. Does anyone have any advice? > > > > > > Regards, > > > Elias > > > > > > make[1]: Leaving directory '/home/emartenson/qubes-builder' > > > make[1]: Entering directory '/home/emartenson/qubes-builder' > > > -> Building core-admin-linux (rpm_spec/core-dom0-linux.spec) for fc23 > > > dom0 (logfile: build-logs/core-admin-linux-dom0-fc23.log) > > > --> Done: > > > > > > qubes-src/core-admin-linux/pkgs/fc23/x86_64/qubes-core-dom0-linux-3.2.12-1.fc23.x86_64.rpm > > > > > > qubes-src/core-admin-linux/pkgs/fc23/x86_64/qubes-core-dom0-linux-debuginfo-3.2.12-1.fc23.x86_64.rpm > > > > > > qubes-src/core-admin-linux/pkgs/fc23/x86_64/qubes-core-dom0-linux-kernel-install-3.2.12-1.fc23.x86_64.rpm > > > -> Building core-admin-linux (rpm_spec/core-dom0-vaio-fixes.spec) for > > > fc23 dom0 (logfile: build-logs/core-admin-linux-dom0-fc23.log) > > > --> Done: > > > > > > qubes-src/core-admin-linux/pkgs/fc23/x86_64/qubes-core-dom0-vaio-fixes-1.6.1-1.fc23.x86_64.rpm > > > make[1]: Leaving directory '/home/emartenson/qubes-builder' > > > make[1]: Entering directory '/home/emartenson/qubes-builder' > > > make[1]: Leaving directory '/home/emartenson/qubes-builder' > > > -> Building core-agent-linux (rpm_spec/core-vm.spec) for fc23 vm > > > (logfile: build-logs/core-agent-linux-vm-fc23.log) > > > --> Done: > > > > > > qubes-src/core-agent-linux/pkgs/fc23/x86_64/python2-dnf-plugins-qubes-hooks-3.2.16-1.fc23.x86_64.rpm > > > > > > qubes-src/core-agent-linux/pkgs/fc23/x86_64/python3-dnf-plugins-qubes-hooks-3.2.16-1.fc23.x86_64.rpm > > > > > > qubes-src/core-agent-linux/pkgs/fc23/x86_64/qubes-core-vm-3.2.16-1.fc23.x86_64.rpm > > > > > > qubes-src/core-agent-linux/pkgs/fc23/x86_64/qubes-core-vm-debuginfo-3.2.16-1.fc23.x86_64.rpm > > > > > > qubes-src/core-agent-linux/pkgs/fc23/x86_64/qubes-core-vm-systemd-3.2.16-1.fc23.x86_64.rpm > > > > > > qubes-src/core-agent-linux/pkgs/fc23/x86_64/qubes-core-vm-sysvinit-3.2.16-1.fc23.x86_64.rpm > > > -> Building core-agent-linux (rpm_spec/core-vm-doc.spec) for fc23 vm > > > (logfile: build-logs/core-agent-linux-vm-fc23.log) > > > --> Done: > > > > > > qubes-src/core-agent-linux/pkgs/fc23/noarch/qubes-core-vm-doc-3.2.16-1.noarch.rpm > > > make[1]: Entering directory '/home/emartenson/qubes-builder' > > > -> Building linux-kernel (kernel.spec) for fc23 dom0 (logfile: > > > build-logs/linux-kernel-dom0-fc23.log) > > > --> Done: > > > > > > qubes-src/linux-kernel/pkgs/fc23/x86_64/kernel-4.4.55-11.pvops.qubes.x86_64.rpm > > > > > > qubes-src/linux-kernel/pkgs/fc23/x86_64/kernel-devel-4.4.55-11.pvops.qubes.x86_64.rpm > > > > > > qubes-src/linux-kernel/pkgs/fc23/x86_64/kernel-qubes-vm-4.4.55-11.pvops.qubes.x86_64.rpm > > > make[1]: Leaving directory '/home/emartenson/qubes-builder' > > > make[1]: Entering directory '/home/emartenson/qubes-builder' > > > -> Building artwork (qubes-artwork.spec) for fc23 dom0 (logfile: > > > build-logs/artwork-dom0-fc23.log) > > > --> build failed! > > > make[2]: Entering directory '/home/emartenson/qubes-builder' > > > /home/emartenson/qubes-builder/qubes-src/builder-fedora//update-local-repo.sh > > > fc23 > > > sudo BACKEND_VMM=xen chroot /home/emartenson/qubes-builder/chroot-fc23 sh > > > -c 'cd /home/user/qubes-src/artwork; dnf --refresh -y update' > > > Dependencies resolved. > > > Nothing to do. > > > Complete! > > > sudo BACKEND_VMM=xen chroot /home/emartenson/qubes-builder/chroot-fc23 sh > > > -c 'cd /home/user/qubes-src/artwork; dnf builddep --allowerasing --best > > > -y qubes-artwork.spec' > > > Package ImageMagick-6.9.2.7-1.fc23.x86_64 is already installed, skipping. > > > Package netpbm-progs-10.75.99-1.fc23.x86_64 is already installed, > > > skipping. > > > No matching package to install: 'qubes-utils >= 3.9.0' > > > Not all de
[qubes-users] Re: Building Qubes from source, strange error.
On Wednesday, March 22, 2017 at 6:45:12 PM UTC+1, Opal Raava wrote: > On Wednesday, March 22, 2017 at 12:01:53 PM UTC+1, lok...@gmail.com wrote: > > I'm trying to build Qubes from source, but when following the instructions > > (https://www.qubes-os.org/doc/qubes-builder/), the build fails with the > > message below. Does anyone have any advice? > > > > Regards, > > Elias > > > > make[1]: Leaving directory '/home/emartenson/qubes-builder' > > make[1]: Entering directory '/home/emartenson/qubes-builder' > > -> Building core-admin-linux (rpm_spec/core-dom0-linux.spec) for fc23 dom0 > > (logfile: build-logs/core-admin-linux-dom0-fc23.log) > > --> Done: > > > > qubes-src/core-admin-linux/pkgs/fc23/x86_64/qubes-core-dom0-linux-3.2.12-1.fc23.x86_64.rpm > > > > qubes-src/core-admin-linux/pkgs/fc23/x86_64/qubes-core-dom0-linux-debuginfo-3.2.12-1.fc23.x86_64.rpm > > > > qubes-src/core-admin-linux/pkgs/fc23/x86_64/qubes-core-dom0-linux-kernel-install-3.2.12-1.fc23.x86_64.rpm > > -> Building core-admin-linux (rpm_spec/core-dom0-vaio-fixes.spec) for fc23 > > dom0 (logfile: build-logs/core-admin-linux-dom0-fc23.log) > > --> Done: > > > > qubes-src/core-admin-linux/pkgs/fc23/x86_64/qubes-core-dom0-vaio-fixes-1.6.1-1.fc23.x86_64.rpm > > make[1]: Leaving directory '/home/emartenson/qubes-builder' > > make[1]: Entering directory '/home/emartenson/qubes-builder' > > make[1]: Leaving directory '/home/emartenson/qubes-builder' > > -> Building core-agent-linux (rpm_spec/core-vm.spec) for fc23 vm (logfile: > > build-logs/core-agent-linux-vm-fc23.log) > > --> Done: > > > > qubes-src/core-agent-linux/pkgs/fc23/x86_64/python2-dnf-plugins-qubes-hooks-3.2.16-1.fc23.x86_64.rpm > > > > qubes-src/core-agent-linux/pkgs/fc23/x86_64/python3-dnf-plugins-qubes-hooks-3.2.16-1.fc23.x86_64.rpm > > > > qubes-src/core-agent-linux/pkgs/fc23/x86_64/qubes-core-vm-3.2.16-1.fc23.x86_64.rpm > > > > qubes-src/core-agent-linux/pkgs/fc23/x86_64/qubes-core-vm-debuginfo-3.2.16-1.fc23.x86_64.rpm > > > > qubes-src/core-agent-linux/pkgs/fc23/x86_64/qubes-core-vm-systemd-3.2.16-1.fc23.x86_64.rpm > > > > qubes-src/core-agent-linux/pkgs/fc23/x86_64/qubes-core-vm-sysvinit-3.2.16-1.fc23.x86_64.rpm > > -> Building core-agent-linux (rpm_spec/core-vm-doc.spec) for fc23 vm > > (logfile: build-logs/core-agent-linux-vm-fc23.log) > > --> Done: > > > > qubes-src/core-agent-linux/pkgs/fc23/noarch/qubes-core-vm-doc-3.2.16-1.noarch.rpm > > make[1]: Entering directory '/home/emartenson/qubes-builder' > > -> Building linux-kernel (kernel.spec) for fc23 dom0 (logfile: > > build-logs/linux-kernel-dom0-fc23.log) > > --> Done: > > > > qubes-src/linux-kernel/pkgs/fc23/x86_64/kernel-4.4.55-11.pvops.qubes.x86_64.rpm > > > > qubes-src/linux-kernel/pkgs/fc23/x86_64/kernel-devel-4.4.55-11.pvops.qubes.x86_64.rpm > > > > qubes-src/linux-kernel/pkgs/fc23/x86_64/kernel-qubes-vm-4.4.55-11.pvops.qubes.x86_64.rpm > > make[1]: Leaving directory '/home/emartenson/qubes-builder' > > make[1]: Entering directory '/home/emartenson/qubes-builder' > > -> Building artwork (qubes-artwork.spec) for fc23 dom0 (logfile: > > build-logs/artwork-dom0-fc23.log) > > --> build failed! > > make[2]: Entering directory '/home/emartenson/qubes-builder' > > /home/emartenson/qubes-builder/qubes-src/builder-fedora//update-local-repo.sh > > fc23 > > sudo BACKEND_VMM=xen chroot /home/emartenson/qubes-builder/chroot-fc23 sh > > -c 'cd /home/user/qubes-src/artwork; dnf --refresh -y update' > > Dependencies resolved. > > Nothing to do. > > Complete! > > sudo BACKEND_VMM=xen chroot /home/emartenson/qubes-builder/chroot-fc23 sh > > -c 'cd /home/user/qubes-src/artwork; dnf builddep --allowerasing --best -y > > qubes-artwork.spec' > > Package ImageMagick-6.9.2.7-1.fc23.x86_64 is already installed, skipping. > > Package netpbm-progs-10.75.99-1.fc23.x86_64 is already installed, skipping. > > No matching package to install: 'qubes-utils >= 3.9.0' > > Not all dependencies satisfied > > Error: Some packages could not be found. > > /home/emartenson/qubes-builder/qubes-src/builder-fedora/Makefile.fedora:106: > > recipe for target 'dist-build-dep' failed > > make[2]: *** [dist-build-dep] Error 1 > > make[2]: Leaving directory '/home/emartenson/qubes-builder' > > Makefile.generic:147: recipe for target 'packages' failed > > make[1]: *** [packages] Error 1 > > make[1]: Leaving directory '
[qubes-users] Re: Building Qubes from source, strange error.
On Wednesday, March 22, 2017 at 12:01:53 PM UTC+1, lok...@gmail.com wrote: > I'm trying to build Qubes from source, but when following the instructions > (https://www.qubes-os.org/doc/qubes-builder/), the build fails with the > message below. Does anyone have any advice? > > Regards, > Elias > > make[1]: Leaving directory '/home/emartenson/qubes-builder' > make[1]: Entering directory '/home/emartenson/qubes-builder' > -> Building core-admin-linux (rpm_spec/core-dom0-linux.spec) for fc23 dom0 > (logfile: build-logs/core-admin-linux-dom0-fc23.log) > --> Done: > > qubes-src/core-admin-linux/pkgs/fc23/x86_64/qubes-core-dom0-linux-3.2.12-1.fc23.x86_64.rpm > > qubes-src/core-admin-linux/pkgs/fc23/x86_64/qubes-core-dom0-linux-debuginfo-3.2.12-1.fc23.x86_64.rpm > > qubes-src/core-admin-linux/pkgs/fc23/x86_64/qubes-core-dom0-linux-kernel-install-3.2.12-1.fc23.x86_64.rpm > -> Building core-admin-linux (rpm_spec/core-dom0-vaio-fixes.spec) for fc23 > dom0 (logfile: build-logs/core-admin-linux-dom0-fc23.log) > --> Done: > > qubes-src/core-admin-linux/pkgs/fc23/x86_64/qubes-core-dom0-vaio-fixes-1.6.1-1.fc23.x86_64.rpm > make[1]: Leaving directory '/home/emartenson/qubes-builder' > make[1]: Entering directory '/home/emartenson/qubes-builder' > make[1]: Leaving directory '/home/emartenson/qubes-builder' > -> Building core-agent-linux (rpm_spec/core-vm.spec) for fc23 vm (logfile: > build-logs/core-agent-linux-vm-fc23.log) > --> Done: > > qubes-src/core-agent-linux/pkgs/fc23/x86_64/python2-dnf-plugins-qubes-hooks-3.2.16-1.fc23.x86_64.rpm > > qubes-src/core-agent-linux/pkgs/fc23/x86_64/python3-dnf-plugins-qubes-hooks-3.2.16-1.fc23.x86_64.rpm > > qubes-src/core-agent-linux/pkgs/fc23/x86_64/qubes-core-vm-3.2.16-1.fc23.x86_64.rpm > > qubes-src/core-agent-linux/pkgs/fc23/x86_64/qubes-core-vm-debuginfo-3.2.16-1.fc23.x86_64.rpm > > qubes-src/core-agent-linux/pkgs/fc23/x86_64/qubes-core-vm-systemd-3.2.16-1.fc23.x86_64.rpm > > qubes-src/core-agent-linux/pkgs/fc23/x86_64/qubes-core-vm-sysvinit-3.2.16-1.fc23.x86_64.rpm > -> Building core-agent-linux (rpm_spec/core-vm-doc.spec) for fc23 vm > (logfile: build-logs/core-agent-linux-vm-fc23.log) > --> Done: > > qubes-src/core-agent-linux/pkgs/fc23/noarch/qubes-core-vm-doc-3.2.16-1.noarch.rpm > make[1]: Entering directory '/home/emartenson/qubes-builder' > -> Building linux-kernel (kernel.spec) for fc23 dom0 (logfile: > build-logs/linux-kernel-dom0-fc23.log) > --> Done: > > qubes-src/linux-kernel/pkgs/fc23/x86_64/kernel-4.4.55-11.pvops.qubes.x86_64.rpm > > qubes-src/linux-kernel/pkgs/fc23/x86_64/kernel-devel-4.4.55-11.pvops.qubes.x86_64.rpm > > qubes-src/linux-kernel/pkgs/fc23/x86_64/kernel-qubes-vm-4.4.55-11.pvops.qubes.x86_64.rpm > make[1]: Leaving directory '/home/emartenson/qubes-builder' > make[1]: Entering directory '/home/emartenson/qubes-builder' > -> Building artwork (qubes-artwork.spec) for fc23 dom0 (logfile: > build-logs/artwork-dom0-fc23.log) > --> build failed! > make[2]: Entering directory '/home/emartenson/qubes-builder' > /home/emartenson/qubes-builder/qubes-src/builder-fedora//update-local-repo.sh > fc23 > sudo BACKEND_VMM=xen chroot /home/emartenson/qubes-builder/chroot-fc23 sh -c > 'cd /home/user/qubes-src/artwork; dnf --refresh -y update' > Dependencies resolved. > Nothing to do. > Complete! > sudo BACKEND_VMM=xen chroot /home/emartenson/qubes-builder/chroot-fc23 sh -c > 'cd /home/user/qubes-src/artwork; dnf builddep --allowerasing --best -y > qubes-artwork.spec' > Package ImageMagick-6.9.2.7-1.fc23.x86_64 is already installed, skipping. > Package netpbm-progs-10.75.99-1.fc23.x86_64 is already installed, skipping. > No matching package to install: 'qubes-utils >= 3.9.0' > Not all dependencies satisfied > Error: Some packages could not be found. > /home/emartenson/qubes-builder/qubes-src/builder-fedora/Makefile.fedora:106: > recipe for target 'dist-build-dep' failed > make[2]: *** [dist-build-dep] Error 1 > make[2]: Leaving directory '/home/emartenson/qubes-builder' > Makefile.generic:147: recipe for target 'packages' failed > make[1]: *** [packages] Error 1 > make[1]: Leaving directory '/home/emartenson/qubes-builder' > Makefile:221: recipe for target 'artwork-dom0' failed > make: *** [artwork-dom0] Error 1 There is a version issue here. The current qubes repo produces a qubes-utils-3.2.3 rpm (qubes-utils is built by the component 'linux-utils' which is indeed built before artwork gets built. But somehow the artwork .spec file requires qubes-utils >= 3.9.0 (that arwork spec file is qubes-builder/qubes-src/artwork-qubes-artwork.spec) So I changed that to >= 3.2.3 and started a fresh build. I'll post my results because I'm not sure if this fixes anything. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[qubes-users] Re: XScreenSaver for dom0 pops up
On Monday, February 27, 2017 at 9:41:20 PM UTC+1, ianr...@gmail.com wrote:
> On Wednesday, October 26, 2016 at 8:43:12 AM UTC-4, John Maher wrote:
> > I'm getting the strangest thing on my screen. I'll be working and the
> > XScreenSaver dialog pops up (indicating the screen is locked) and the
> > screen goes black. However, the screen is not locked. I have to move a
> > window around to redraw my screen. This has always happened since I started
> > using Qubes about 3 weeks ago. There appears to be no pattern that prompts
> > this response. Bizarre! Any thoughts?
> >
> > Thanks.
> >
> > John
>
> I found that this happened when I had the Qubes VM Manager set to appear on
> all desktops ("Always on Visible Worksace"). When I stopped that, it stopped
> the problem. Tried this 5 or 6 times on 2 different machines. Running v.3.2
> with and without Feb. updates; no difference.
>
> HTH,
>
> --Ian
Oh that's interesting, I found that disabling the compositor (Menu>System
Tools>Window Manager Tweaks>Compositor) solves the problem for me and also for
somebody else on the github tracker entry.
I can't find the 'always on visible workspaces' settings, but I also lost the
tray icon for the Qubes VM Manager somehow.
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/db357031-8491-4831-9770-0327c085db72%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] XScreenSaver for dom0 pops up
On Friday, November 4, 2016 at 6:34:57 PM UTC+1, John Maher wrote: > On Thursday, November 3, 2016 at 12:50:13 AM UTC-4, Andrew David Wong wrote: > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA512 > > > > On 2016-11-02 08:56, John Maher wrote: > > > On Thursday, October 27, 2016 at 12:42:18 AM UTC-4, Andrew David Wong > > > wrote: > > > On 2016-10-26 15:53, Gaijin wrote: > > On 2016-10-26 13:38, John Maher wrote: > > > On Wednesday, October 26, 2016 at 9:05:48 AM UTC-4, Gaijin wrote: > > >> On 2016-10-26 12:43, John Maher wrote: > > >>> I'm getting the strangest thing on my screen. I'll be working and > > >>> the > > >>> XScreenSaver dialog pops up (indicating the screen is locked) and > > >>> the > > >>> screen goes black. However, the screen is not locked. I have to > > >>> move a > > >>> window around to redraw my screen. This has always happened since I > > >>> started using Qubes about 3 weeks ago. There appears to be no > > >>> pattern > > >>> that prompts this response. Bizarre! Any thoughts? > > >>> > > >>> Thanks. > > >>> > > >>> John > > >> > > >> Yeah. I had the same thing happen when I upgraded to R3.2 as well. I > > >> asked the same thing but nobody replied. > > >> https://groups.google.com/forum/#!topic/qubes-users/xjHi2TcYBAQ > > >> > > >> It still happens from time to time. Seems to happen less if I have a > > >> lot > > >> of free memory. Closing down some memory hungry AppVMs seems to > > >> lessen > > >> it, but I haven't been able to specifically replicate it. > > > > > > Interesting, because I think I have more than enough memory (32 GB). > > > Thanks. > > > > I've got 16GB myself. It's not that the memory is full, but it seems > > to happen more when I have a lot of VMs open in one desktop. That may > > just be a coincidence though. > > > > I'm glad to see it wasn't just me though. I never had this happen with > > earlier versions of Qubes on the same hardware. Not sure if it might > > be the XFCE or a video driver issue. (I've never installed the nVidia > > drivers.) > > > > > > > > Thank you both for reporting this. Gaijin, I'm sorry I missed your thread. > > > > > > Just to confirm: Are you both using Xfce4? > > > > > > Tracking the issue here: > > > > > > https://github.com/QubesOS/qubes-issues/issues/2399 > > > > > > > > > Sorry for the delay in responding. I used the default install for 3.2. > > > > > > I also just noticed that it appears that memory is not being purged when > > > apps are closed. Today when I "woke up" the screen from one of these odd > > > screen saver like issues, it very briefly displayed a browser window with > > > a site I was on yesterday. I looked carefully and confirmed that I did > > > not actually have that window open on my system. It's as if something > > > from yesterday's memory was sent to the screen and then closed. Rather > > > disconcerting. > > > > > > John > > > > > > > I don't think that should necessarily be disconcerting. The Qubes security > > model does not include or rely upon purging memory at any particular time > > interval. It assumes that you, the authentic single user, should be the > > only one with access to dom0's screen content. So, the fact that you're > > allowed to see your screen content from yesterday doesn't constitute any > > violation of the security model. You're still the same trusted user as you > > were yesterday. (If I've misunderstood your concern, please let me know.) > > > > - -- > > Andrew David Wong (Axon) > > Community Manager, Qubes OS > > https://www.qubes-os.org > > -BEGIN PGP SIGNATURE- > > > > iQIcBAEBCgAGBQJYGsH3AAoJENtN07w5UDAwKtIP/2vblyc4Rf9uwU3M+WGv2K7V > > T7VoTDfGjB8XWyX6LZW/TrtameFmAj/Rb0bINOrIWpkrP9RdNUm+0/BR10NkcLul > > FqaxMOcl2u2Tk775VjYtC+Z7y1ycJDQjaMvtqrdDQkeGhMumzcDOHD9RufTFSIRm > > 8ke7GxfMQBH7R0DJ5E26B7HZJg73k1RKFT5BbpmKrfHxBBEaJTUALeNFZnp2ekl+ > > HrRV4u8+T/Tbwzha5e/iTvJEVTMcMxzD4uziaN+TfiK2Iwp40w0W8IdmRjPzdkLI > > +PDhAfjpQCEcZIPT/V+u6GsMhUDJo5ABPs/as17YY4b8VMwm9F7/J2Oo6nfwl/Rh > > gOnwVLFQKUtq3iaNbORDzAjBSEny6wYKlfvpL3IWGAHhH0mbP5j1ivSJoF+navuD > > qPMvMyAuhFh7hSsTPJ0CTMrDZYTGVlSryLrvXUwl5Lf6zplXRxO6uGu3ruUnepxR > > 9izVXApPBv/Cc41G3wrCUGN3deE1OpzNSxhQS+NK4B3kJSGAm4+Zi/F/B8yiR6Lt > > L/DiLI04X1LZ/XW+ZrKKiQbqVKAzeDqkDPW1D4POEckQnEfPqMcc32LzQVf6ORvX > > Xzjn+UhUcdTzINAuISwYeBdvBTk6Wk80T80nChZJdnSdWi6klvbcof96UNdD3sja > > swBLAb3aU4hobRxFAcL7 > > =Fv0E > > -END PGP SIGNATURE- > > If the memory that temporarily renders to the screen is as isolated from > other appvms as expected rendered content (like an open windows), then, yes, > I'm not concerned about leakage from one environment to another. > > I will say that it is simply disconcerting to see it display, security > implications aside. More important to me, though, is the hope that this > "screen
[qubes-users] Any suggestions for a video card that will actually work in a home-built desktop rig?
Hi all, I built a desktop rig for use with qubes, but when the graphics gets initialized i get a black screen. I'm using the Intel HD Graphics 530 of my i5-6500. Does anybody know a cheap pci-e, hdmi out video card that I can use and that will work with qubes? -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/efab1b93-1bd7-41cd-ab4c-df3055623d45%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Graphics card problem with Intel HD Graphics 530
On Monday, January 30, 2017 at 11:54:15 PM UTC+1, Opal Raava wrote: > Hi all, > > I've been running QUbes OS for a while, an I built a new PC with an intel > i5-6500 cpu and intel hd graphics 530 card. When I just install fedora25 > workstation on it, the graphics look cool, 3d is fast enouhg. When I boot > from the disk of my old computer the screen gets black at the point the gray > screen with progress bar should be. I checked grub and it does give the > i915.whatever=1 to the linux commandline. > > Any ideas? should I perhaps buy some old compatible graphics card and just > use that? Oh sorry, I didn't mean that i installed a HVM with Fedora25. I'm installing Qubes on a new machine, an i5-6500. it has an SSD (on which i want to install Qubes :) and a HDD that boots me into Fedora25, which works with my graphics card. If I however run the setup of Qubes R3.2 I get a black screen right when the graphical installer should run. But since it works for you, I'm gonna try to change some settings in my bios. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/f74e9708-cd32-4cd7-8086-801d6f31a57f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Graphics card problem with Intel HD Graphics 530
Hi all, I've been running QUbes OS for a while, an I built a new PC with an intel i5-6500 cpu and intel hd graphics 530 card. When I just install fedora25 workstation on it, the graphics look cool, 3d is fast enouhg. When I boot from the disk of my old computer the screen gets black at the point the gray screen with progress bar should be. I checked grub and it does give the i915.whatever=1 to the linux commandline. Any ideas? should I perhaps buy some old compatible graphics card and just use that? -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/53e365b2-0277-48a1-b589-f4db2e219916%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Windows HVM and two monitors (dual head - dual headache ;-) ). Help appreciated.
On Tuesday, January 17, 2017 at 10:23:15 AM UTC+1, daltong defourne wrote: > Well, first, the good thing: > Dual head windows HVM booted without issue. > > (Qubes proper is also working with the second monitor and extending the qubes > desktop to it, all fine) > > Now, the bad thing - apparently, enabling "extend desktop to this monitor" in > windows does literally nothing (seamless GUI disabled) > > The second monitor still shows qubes desktop wallpaper. > > Going fullscreen does nothing (windows VM occupies first screen allright, > second screen remains "qubes wallpaper") > > So far I am working around the following manner: > I disable second monitor in windows, then make windows VM's window "snap" to > minimum size by dragging it upwards, then extend it so it covers both > monitors in "qubes view" > > Then I manage my windows in Windows (pardon the pun) with winsplit revolution > (The only window splitter thingie that worked okay in Qubes VM for me) > > What I'd like is capability for non-seamless windows VM to go into "full > full" screen and occupy both monitors while doing so (in order not to waste > any "pixel estate" to window borders and panel and such) I dont know much about this topic as I dont have a dual screen. What I do know is that 'full full' screens are not really something you would want. A malicous software could grab that 'full full' screen and start asking for sensitive information. I also had an issue with 'full full' screen and then using RDP (that's what I use windows for anyway) and then not being able to regain control into my dom0 window manager, because something crashed or got stuck I was actually forced to reboot my machine. I ended up using windows non-seamless, as a 'qubes-normal full screen' on my very last xfce desktop. thats where my windows lives and I'm happy with that setup. Your situation is different, but this is just my two cents on how it works best for me. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/3ae2e70d-106a-4d7c-aa2c-0db787a72ecf%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Qubes 3.2 Dom0 no longer updating.
Hi all, Since about a week or so, I'm unable to update dom0 the way I used to. The VM Manager will tell me there are updates available for Dom0, and when I click 'Update VM' I see the familiar 'downloading updates' but after that the window with the updates never appears. If I run qubes-dom0-update it tells me 'No updates available' Does this perhaps have to do with fedora23/fedora24 issues? I asked on IRC and one person is having this issue as well. Is anybody else having this issue? -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/34ca6f88-67fe-4f86-83e0-1599adaebe9c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Playing with docker in an app-vm
10.137.2.0/24 is a network specification of all hosts, a way of saying 10.137.2.*, i dont think the ip number of the sys-firewall comes into it. Its probably got an ip of 10.137.2.1 orso -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/58e0d248-43ec-47f4-8ff7-a1f12e478790%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Playing with docker in an app-vm
On Thursday, November 24, 2016 at 5:30:52 PM UTC+1, Grzesiek Chodzicki wrote: > W dniu czwartek, 24 listopada 2016 14:05:30 UTC+1 użytkownik Opal Raava > napisał: > > Hi all, > > > > I've not seen many docker posts, but for the heck of it I'd like to report > > on how I made an app-vm that has a website running in docker and reachable > > by everything connected to sys-firewall. > > > > 1) install docker in fedora-24, dnf install docker > > > > 2) create the new appvm, I called it 'docker' > > > > 3) in that app-vm in /rw/config/rc.local, i put: > > > > rm -rf /var/lib/docker > > ln -s /home/user/docker /var/lib/docker > > systemctl start docker > > > > , and I made the dir in /home/user/docker > > now as root i can use 'docker ps' and everything. > > > > > > 4) networking, making 'docker' visible: > >on docker app-vm in /rw/config/qubes-firewall-user-script, i put: > > > > iptables -I INPUT -s 10.137.2.0/24 -j ACCEPT > > > >on sys-firewall, in /rw/config/qubes-firewall-user-script, i put: > > > > iptables -I FORWARD 2 -s 10.137.2.0/24 -d $(docker-appvm-ip) -j ACCEPT > > > > Ok, that's all i have on docker, and it works great. > > 10.137.2.0?24 is the IP addres of your sys-firewall machine, right? I'm > trying to apply a similar configuration to my qubes instance. Yea, it's the network provided by sys-firewall. I look at the ip number of an appvm using sys-firewall to figure out my net(mask) -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/f1406c9e-521f-4fc2-9075-5b1965a31c60%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Network problem since upgrade to fedora-24 template
On Thursday, November 24, 2016 at 3:03:01 PM UTC+1, BePe wrote: > Hi Opal, > Thanks. > But I don't know all the actions that should be realized. For sur there > will be IP configuration, routing and probably iptables rules. > BePe > > On 11/24/2016 01:22 PM, Opal Raava wrote: > > On Thursday, November 24, 2016 at 8:33:14 AM UTC+1, BePe wrote: > >> Hi All, > >> > >> I have an installation of QubeOS 3.2 inside a KVM VM (I know > >> that it's not recommended but it's very practical for testing) > >> that was working without any major issue since last week when I > >> decided to upgrade to the fedora-24 template and have migrated > >> the net-vm et the firewall-vm to use the new template. > >> > >> Since then, the networking (e.g. internet access) is no longer > >> working on all the AppVM except on the net-vm. > >> > >> I noted that when an AppVM is started there is no vif interface > >> that is brought up in its configured NetVM as it used be the > >> case when fedora-23 template was used for the NetVM. > >> > >> Does somebody have the same issue? How could I fix/workaround > >> the problem? > >> > >> Is there a way to manually and properply bring up the vif.XX > >> interface to establish the connection between a VM and its > >> configured NetVM? > >> > >> Thanks for your help. > >> > >> Regards, > >> > >> > >> -- > >> BePe > > Hi BePe, I don't have the same issue, but maybe you can manually put the > > required ifconfig orso commands in your /rw/config/rc.local file? (and make > > that file executable.) > > > > -- > BePe Hmm there should be an easier way, but I dont know how... I'm still a noob :/ -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/3aeefa65-95be-4a8a-9a89-5f4c9772ea4f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Playing with docker in an app-vm
On Thursday, November 24, 2016 at 2:05:30 PM UTC+1, Opal Raava wrote: > Hi all, > > I've not seen many docker posts, but for the heck of it I'd like to report on > how I made an app-vm that has a website running in docker and reachable by > everything connected to sys-firewall. > > 1) install docker in fedora-24, dnf install docker > > 2) create the new appvm, I called it 'docker' > > 3) in that app-vm in /rw/config/rc.local, i put: > > rm -rf /var/lib/docker > ln -s /home/user/docker /var/lib/docker > systemctl start docker > > , and I made the dir in /home/user/docker > now as root i can use 'docker ps' and everything. > > > 4) networking, making 'docker' visible: >on docker app-vm in /rw/config/qubes-firewall-user-script, i put: > > iptables -I INPUT -s 10.137.2.0/24 -j ACCEPT > >on sys-firewall, in /rw/config/qubes-firewall-user-script, i put: > > iptables -I FORWARD 2 -s 10.137.2.0/24 -d $(docker-appvm-ip) -j ACCEPT > > Ok, that's all i have on docker, and it works great. Edit: your network is perhaps different from 10.137.2.0/24, sorry -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/2ea4f819-2a9c-42b3-9b03-cc37c95d4eea%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Windows 7 Install Hangs At Starting Page
On Thursday, November 24, 2016 at 12:59:04 PM UTC+1, David Wylie wrote: > I just get the "Starting Windows" and the glowing logo on a black screen. > Left it for an hour, nothing else happens. > > I found this which doesn't seem relevant (or if it is I can't make the > connection) : > > https://groups.google.com/forum/#!searchin/qubes-users/starting$20windows$20hang%7Csort:relevance/qubes-users/2q19jFeTFGk/DgL6a67_CAAJ > > Is there anything generally I should be looking for? > > Thanks, I have win 7 as my windows HVM, if I remember correctly, you need to have windows 7, and not windows home. The windows-tools-package that qubes uses is only for win 7. There is a great page on all this at: https://www.qubes-os.org/doc/windows-appvms/ -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/eaf901eb-d07c-4868-b7a2-b1cde68d448c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] How to update fedora-23-dvm to fedora-24?
Hi, I updated everything to fedora-24 template, but I don't know how to update fedora-23-dvm. It uses the old fedora-23 template and when i change this in the manager to use fedora-24, it says making save file but then no browser or terminal runs. What is the best way to update fedora-23-dvm? -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/5cd2857d-474a-406e-8145-6cbf8037185b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
