cker list looks short, but there are definitely some
>> tests that have not been run.
>
> Last I checked, flatpak was still broken. Will retest this week.
What's broken with flatpak? I've been using several flatpaks OK since 'dnf
system-upgrad
h.service so that it omits --plymouth from
systemd-tty-ask-password-agent?
--
Chris Murphy
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Fedora Code of Conduc
--
Chris Murphy
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https
in the Cloud Working
> group.
>
> - [David Duncan]
> - [Dusty Mabe]
> - [Major Hayden]
> - [Neal Gompa]
> - [Davida Cavalca]
> - [Michel Salim]
> - [Amy Marrich]
> - [Joe Doss]
Chris Murphy : chrismurphy
--
Chris Murphy
___
this
meeting isn't going to happen. Next meeting scheduled for Dec 9.
--
Chris Murphy
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedor
be of any
> help?
>
Thanks for the report. I've filed this issue
https://pagure.io/fedora-web/websites/issue/220
Looks like the images are available in AWS, but just aren't listed at
alt.fedoraproject.org/cloud
--
Chris Murphy
___
cloud mailing list
ting.2021-11-11-15.00.txt
> Log:
> https://meetbot-raw.fedoraproject.org/teams/fedora_cloud_meeting/fedora_cloud_meeting.2021-11-11-15.00.log.html
Sorry I missed the meeting, but yeah +1 to (re)making Cloud Edition
officially as an edition
--
Chris Murphy
asked the XFS maintainer about all of this and he said
fallocate'd swapfiles should work. And I also tested it with kernel
5.11.16 and 5.12 and it does work.
--
Chris Murphy
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send
u can use a newer
kernel that doesn't have the bug.
Or like Dusty suggests, give the Fedora 34 Cloud images a whirl. Out tomorrow!
--
Chris Murphy
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@list
a preallocation, if the workload were to
never need swap, it has a nearly zero cost. If you aren't using some
swap, aren't you in a sense overprovisioning memory?
--
Chris Murphy
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an em
On Mon, Jun 1, 2020 at 12:44 PM Simo Sorce wrote:
>
> On Mon, 2020-06-01 at 10:37 -0600, Chris Murphy wrote:
> > Thanks for the early feedback!
> >
> > On Mon, Jun 1, 2020 at 7:58 AM Stephen Gallagher
> > wrote:
> > > * Reading through the Change, you
ht. Fixed.
I suggest these three lines in the configuration (I've updated the
change proposal how to test section to include this):
[zram0]
memory-limit = none
zram-fraction = 0.5
There is no cap functionality yet in the generator.
--
Chris Murphy
___
clou
. It might be an
option to ship different configurations, if necessary.
There is a test day planned. But I'd like to get solid buy-in from
cloud and server folks before then.
Thanks,
--
Chris Murphy
___
cloud mailing list -- cloud@lists.fedoraproject.org
use cases.
Resource Control (2019) Dan Schatzberg
https://www.youtube.com/watch?v=30i7SamZxRU
I'm looking into setting up a discussion session with Dan, and do some
Q I'll report back when I know more about that.
--
Chris Murphy
___
cloud mailing
On Mon, Jan 13, 2020 at 10:51 AM Dusty Mabe wrote:
>
>
>
> On 1/8/20 5:21 PM, Chris Murphy wrote:
> > On Mon, Jan 6, 2020 at 7:56 PM Dusty Mabe wrote:
> >>
> >> For cloud at least it's very common to not have swap. I'd argue for servers
> >> you
ile for certain use cases like
hibernation. So I'm curious if this might have broader appeal, and get
systemd-zram generator production ready.
--
Chris Murphy
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an em
SCo
vote. But as a short term solution while evaluating more sophisticated
solutions, I think this is a good call so I thought I'd just mention
it, in case you folks want to be included in the change.
--
Chris Murphy
___
cloud mailing list -- cl
e original unit file, edit it,
and use it as a drop in unit file in /etc ?
Unfinished change, still in progress...
https://fedoraproject.org/wiki/Changes/EnableFSTrimTimer
--
Chris Murphy
___
cloud mailing list -- cloud@lists.fedoraproject.org
To
On Wed, Dec 18, 2019 at 11:10 AM Neal Gompa wrote:
>
> On Wed, Dec 18, 2019 at 12:08 PM Chris Murphy wrote:
> >
> > On Wed, Dec 18, 2019 at 10:56 AM Chris Murphy
> > wrote:
> > >
> > > One thing I see in the Ubuntu fstrim.service unit file that I'm not
On Wed, Dec 18, 2019 at 10:56 AM Chris Murphy wrote:
>
> One thing I see in the Ubuntu fstrim.service unit file that I'm not
> seeing in the Fedora fstrim.service unit file, is a conditional for
> containers (line 4). I'm not sure where to ask about that. Maybe
> upstream systemd?
readd cloud@ list
On Wed, Dec 18, 2019 at 5:32 AM Martin Kolman wrote:
>
> On Wed, 2019-12-18 at 13:11 +0100, Martin Pitt wrote:
> > Hello Chris,
> >
> > Chris Murphy [2019-12-17 22:23 -0700]:
> > > This desktop@ thread [1] about a slow device restored by enab
ect.org/wiki/Changes/EnableTrimOnDmCrypt
[5]
Trim on LUKS/dm-crypt note from upstream, section 5.19
https://gitlab.com/cryptsetup/cryptsetup/-/wikis/FrequentlyAskedQuestions#5-security-aspects
--
Chris Murphy
___
cloud mailing list -- cloud@lists.fedoraproject.org
chrismurphy added a new comment to an issue you are following:
``
I read a list of problems already with negative arguments, not supplied by me.
And I've presented something that obviates literally all of them. I see it as
advice, not debate.
``
To reply, visit the link below or just reply to
chrismurphy added a new comment to an issue you are following:
``
Yeah I wasn't considering anything we don't have in anaconda, but then also
anything not already in the Fedora kernel for some time now.
Plus ZFS lacks fs shrink, and so you can't remove block devices arbitrarily, it
also lacks
chrismurphy added a new comment to an issue you are following:
``
Ahh sorry, I kinda figured realistically there are only three options: ext4,
XFS, and Btrfs, and the only one not mentioned so far is Btrfs.
There's some hits of people using it in AWS contexts, but I have not yet run
across
chrismurphy added a new comment to an issue you are following:
``
All the partitioning, sizing, and resizing concerns mentioned in this issue
vanish with a certain other filesystem, which does all resizes (grow, shrink,
add and remove devices) online and atomically and typically in a single
chrismurphy reported a new issue against the project: `fedora-atomic` that you
are following:
``
Version:
I tested this Fedora-Atomic-ostree-x86_64-26-20170619.n.0.iso on an Intel NUC
(a baremetal installation).
Problem, Actual results:
The installation media and environment has wireless
chrismurphy added a new comment to an issue you are following:
``
OK this seems bad
plymouth-start.service: Executing: /usr/sbin/plymouthd --mode=boot
--pid-file=/var/run/plymouth/pid --attach-to-session
[3.372107] general protection fault: [#1] SMP
[3.372654] Modules linked in:
chrismurphy added a new comment to an issue you are following:
``
VM install of Fedora-Atomic-ostree-x86_64-25-20170118.1.iso to a clean LV
succeeds, for both BIOS and UEFI firmware. Using default partitioning, the
required layout is created. Both installations completely startup, I can login,
chrismurphy added a new comment to an issue you are following:
``
Sorry for the confusing report.
docker-root-lv was created automatically when
/etc/sysconfig/docker-storage-setup contained
>STORAGE_DRIVER=overlay2
DOCKER_ROOT_VOLUME=yes>
Upon stopping docker and issuing atomic storage reset,
chrismurphy added a new comment to an issue you are following:
``
>dustymabe
>Am I missing something? Did I make some bad assumptions somewhere in this test?
Nope, works for me as well. /var is still a directory on the ext4 rootfs, but
it looks like a new LV Is created at 40% of the free space
chrismurphy added a new comment to an issue you are following:
``
> dustymabe
> with DOCKER_ROOT_VOLUME and overlayfs using that then all of /var/lib/docker
> would be taken care of. Please let me know if I'm wrong.
It'll work on a conventional installation. I'm skeptical it'll work on an
chrismurphy added a new comment to an issue you are following:
``
>vgoyal
>IIUC, you are saying that use a thin LV for rootfs to work around xfs shrink
>issue? People have tried that in the past and there have been talks about that
>many a times. There are still issues with xfs on top of thin
chrismurphy added a new comment to an issue you are following:
``
Flipping from one to the other will take free space somewhere for the 'atomic
storage export/import' operation to temporarily store docker images and
containers to.
A way around the xfs lack of shrink issue is to put the
chrismurphy added a new comment to an issue you are following:
``
dwalsh mentioned the a way to flip between them
https://www.spinics.net/linux/fedora/fedora-cloud/msg07620.html
Missing from that sequence is actually configuring the new storage if it
doesn't exist yet.
I think putting custom
but documenting a
strategy for migrating to overlay is OK.
--
Chris Murphy
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
thinly provisioned
storage; stop docker and change the configuration to use overlay
instead of device mapper driver; start docker, import all the tar'd
containers.
--
Chris Murphy
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
chrismurphy added a new comment to an issue you are following:
``
[](/atomic-wg/issue/raw/files/cb8148271c4c88af8e1abebf3d2b725e0f44eaa2ffc65b837c6424c061eb4755-program.log)
chrismurphy added a new comment to an issue you are following:
``
Fedora-Atomic-ostree-x86_64-25-20161207.0.iso in virt-manager set to use UEFI;
and default automatic partitioning.
program.log
12:04:03,606 INFO program: Running... efibootmgr
12:04:03,647 INFO program: EFI variables are not
on netinstalls and lives. And /bin/sh does
exist, it's a symlink to bash and /bin/bash does exist also. So I'm
still confused.
Chris Murphy
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
and automatically use them, so we can better
figure out what works well, and what works poorly, for various use
cases.
Chris Murphy
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
fe time, you can swap out Cloud for Atomic to
underscore the new emphasis.
I think it's right to say instead of pressure cooker May and November,
that it's a lighter effort more broadly distributed. I don't see a big
problem with a change in branding midstream for a release, but I'm not
a marketing type.
--
Chris Murphy
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
er chance of guessing
what's going on than the logs indicate. This makes it difficult to get
contributors involved. And makes it damn near impossible any of them
would want to become even intermediately competent - it's a heavy
investment.
--
Chris Murphy
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
at.com/show_bug.cgi?id=1380866
Does this need to be marked as a freeze exception to back the change
out for beta candidate images to work?
--
Chris Murphy
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Cloud Base images to
non-release blocking. And then whatever contingency for that side bar
link if the Cloud Base images aren't available for release day.
--
Chris Murphy
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Still hitting this crash with a default installation of
Fedora-Atomic-dvd-x86_64-25-20160921.n.0.iso
https://bugzilla.redhat.com/show_bug.cgi?id=1375702
--
Chris Murphy
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send
ud@lists.fedoraproject.org
> To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
>
--
Chris Murphy
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
:40 bios_xfs.qcow2
Btrfs and XFS take seconds to completely initialize. Ext4 defaults
took 6 minutes, and with -i 4096 it took 8 minutes to complete lazy
init.
--
Chris Murphy
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send
On Fri, Sep 16, 2016 at 2:15 PM, Chris Murphy <li...@colorremedies.com> wrote:
> You'd need to
> run all this by them and see if there's a way to do a mkfs.ext4 -i
> 4096 for just Atomic Host installations, there's no point doing that
> for workstation installations. Or just
On Fri, Sep 16, 2016 at 10:56 AM, Chris Murphy <li...@colorremedies.com> wrote:
> Inode exhaustion?
>
> If the installer is going to create the file system used for overlayfs
> backing storage with ext4, that probably means mkfs.ext4 -i 4096 will
> need to be used; so how doe
ivial pursuit is this "the GPT priority attribute" which I can find
no where else, but I rather like this idea of using an xattr on a
directory as the hint for which fs tree the bootloader should use
rather than writing out new bootloader configurations.
problems before they get worse.
[1]
http://www.spinics.net/lists/linux-btrfs/msg53410.html
[2] semi random example
http://oss.sgi.com/cgi-bin/gitweb.cgi?p=xfs/cmds/xfstests.git;a=blob;f=tests/btrfs/060
--
Chris Murphy
___
cloud mailing list
cloud@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org
On Sat, Sep 10, 2016 at 10:45 PM, Dusty Mabe <du...@dustymabe.com> wrote:
>
>
> On 09/11/2016 12:22 AM, Dusty Mabe wrote:
>>
>>
>> On 09/10/2016 12:47 PM, Chris Murphy wrote:
>>> On Fri, Sep 9, 2016 at 9:28 PM, Dusty Mabe <du...@dustymabe.c
On Sat, Sep 10, 2016 at 12:05 PM, Chris Murphy <li...@colorremedies.com> wrote:
> Could be related this bug, I see the same error there after Disks
> changes partitioning, and the old partition table is being used. A
> feature for Fedora 25 is udisks is replaced by storaged
, so this might be a goose chase.
Error setting partition type after formatting
https://bugzilla.redhat.com/show_bug.cgi?id=1374334
Chris Murphy
___
cloud mailing list
cloud@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/cloud
he best log,
it doesn't report the actual commands its using and the exit code for
each command. So we're left wondering if partprobe was called or not.
Maybe it's being called but is missing in the image?
--
Chris Murphy
___
cloud mailing list
cloud@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org
> For the typical Fedora workstation user, what is needed to migrate to Fedora
> Atomic as a desktop? Does this make it easier to use remote cloud resources?
These might be better asked on desktop@ list where the Workstation WG
and users can put in the
es being produced and I have no idea if they're
really needed. That a release blocking image (cloud base qcow2) nearly
caused F25 alpha to slip because it was busted at least suggests it
probably shouldn't be release blocking anymore. FWIW, cloud ba
doesn't fix
the problem, the -4 version had to be removed first. So in particular
for atomic users this is not good because neither rollback nor updates
will fix the problem. And I don't know what the problem is, so I don'
t know how to fix it other than with the dnf remove hammer.
--
Chris Murphy
On Tue, Apr 19, 2016 at 2:48 PM, Adam Williamson
<adamw...@fedoraproject.org> wrote:
> On Tue, 2016-04-19 at 13:48 -0600, Chris Murphy wrote:
>> Any i686 package that fails to build means it's failed for all primary
>> archs, because i686 is a primary arch. And a failed bu
On Tue, Apr 19, 2016 at 2:48 PM, Adam Williamson
<adamw...@fedoraproject.org> wrote:
> On Tue, 2016-04-19 at 13:48 -0600, Chris Murphy wrote:
>
>> From my limited perspective, such non-functional failure held up
>> release when it violated a release criterion in ef
> I really think it would help if we use these terms carefully and
> precisely, and if we're going to re-define them in any way, make that
> clear and explicit.
It's best to assume I don't understand the terms well enough to use
them precisely, rather than as
block on i686 in general for upgrading, I'd
agree, even though it's a pain.
For Cloud, maybe the way forward at worst is to support Cloud Atomic.
And the images are i686 only? Of course that assumes any problems with
binutil and kernel, or whatever else comes up, is sanely fixab
On Fri, Mar 11, 2016 at 10:14 AM, Dennis Gilmore <den...@ausil.us> wrote:
> On Friday, March 11, 2016 9:58:54 AM CST Chris Murphy wrote:
>> Hi,
>>
>> The installer autopart in Cloud Atomic ISO leaves a bunch of free
>> space in the VG, which on first boot is turned
the installer's autopartitioning behavior. The
kickstart file says it's using autopart, it doesn't have a breakdown
of what it's asking the installer to do, so I guess by virtue of it
being a Cloud productized installer it knows to do this.
Suggestions?
--
Chris Murphy
the cache, the
browser was consistently requesting the old wrong name from mirrors
even though Fedora's servers were supplying the correct new filename.
It's like a 20+ year old bug that makes "clear your browser cache"
sound sane.
--
Chris Murphy
___
we cannot find your kernels ##which btw is awesome
http://dl.fedoraproject.org/pub/alt/atomic/stable/Cloud_Atomic/x86_64/iso/Fedora-Cloud_Atomic-x86_64-23-20160127.iso
Not Found
The requested URL
/pub/alt/atomic/stable/Cloud_Atomic/x86_64/iso/Fedora-Cloud_Atomic-x86_64-23-20160127.iso
was not found on
On Thu, Jan 28, 2016 at 1:19 PM, Matthew Miller
<mat...@fedoraproject.org> wrote:
> On Thu, Jan 28, 2016 at 12:01:34PM -0700, Chris Murphy wrote:
>> http://mirrors.rit.edu/fedora/alt/atomic/stable/Cloud_Atomic/x86_64/iso/Fedora-Cloud_Atomic-x86_64-23-20160127.iso
>
>
On Thu, Jan 28, 2016 at 5:25 PM, Matthew Miller
<mat...@fedoraproject.org> wrote:
> On Thu, Jan 28, 2016 at 03:46:05PM -0700, Chris Murphy wrote:
>> >> http://mirrors.rit.edu/fedora/alt/atomic/stable/Cloud_Atomic/x86_64/iso/Fedora-Cloud_Atomic-x86_64-23-20160127.iso
>
, and is envisioned to only get called by
e.g. ostree admin deploy/switch, or rpm-ostree rollback/upgrade, etc.
That's fine, it's just not obvious what user space tools belong to the
user.
Chris Murphy
___
cloud mailing list
cloud@lists.fedoraproject.org
http
idea whether 'ostree admin instutil' is user domain
or just meant as helpers for some other scripts. So I think we need to
know what the deprecated and new knobs are.
--
Chris Murphy
___
cloud mailing list
cloud@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org
On Tue, Dec 22, 2015 at 1:31 PM, Chris Murphy <li...@colorremedies.com> wrote:
> On two UEFI systems, one with F23 Workstation, the other with F23
> Cloud Atomic, I'm finding the grubx64.efi do not have the same hash,
> even though rpm -q reports the same rpm in
it'll fail UEFI Secure Boot code signing
checks.
--
Chris Murphy
___
cloud mailing list
cloud@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org
OK really weird.
Tree 29.34 is deployed, and I just ran:
# rpm-ostree rollback
This writes out a correct grub.cfg (uses linuxefi/initrdefi) and it
wrote the grub.cfg in the correct location
(/boot/efi/EFI/fedora/grub.cfg). And this grub.cfg works regardless of
which menu entry I pick in GRUB.
(efibootmgr works, and Secure Boot is
enabled). So something's got grub2-mkconfig awfully confused about
what kind of firmware this system has. And then it also tells grub the
-o destination path incorrectly.
Chris Murphy
___
cloud mailing list
cloud
/grub.cfg at all... neither of the correct locations got a
grub.cfg. The correct grub.cfg (minus the wrong linux command) is in
/boot/loader.0.
Wonky.
Chris Murphy
___
cloud mailing list
cloud@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists
rpm-ostree entry .conf
http://fpaste.org/301944/45030746/
What translates this file's linux/initrd into either linux16/initrd16
vs linuxefi/initrdefi?
--
Chris Murphy
___
cloud mailing list
cloud@lists.fedoraproject.org
http://lists.fedoraproject.org
ater
is a better understood process, can be done faster, and requires fewer
resources. And by later, I mean once spcs and overlay stuff are a.
more mature b. better understood c. people doing that work have time
to do it.
The hardware specific utils could go in a metapackage that's
uot;Fedora Cloud Server" is an option in there. This is a conventionally
updated (with dnf) system, it's not an atomic host system.
--
Chris Murphy
___
cloud mailing list
cloud@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org
On Tue, Dec 15, 2015, 5:49 PM Chris Murphy <li...@colorremedies.com> wrote:
It seems to me the easier thing to do is tolerate baking more stuff
into the images and ISO.
OK I just rewound this in my head, and said WTS out loud. There's one cloud
atomic tree, right? So adding a bunch of ha
On Sun, Dec 13, 2015 at 8:29 PM, Chris Murphy <li...@colorremedies.com> wrote:
> It's also best practices to disable the write cache on all drives used
> in any kind of RAID.
More important, all drives in RAID need SCT ERC set on each drive,
which is also not persistent on non-enter
a new one for the
change to be visible to these tools. If I replace or add drives, will
I need to restart the container running smartd? If yes, that'd kinda
be a regression. Maybe I'm doing something wrong, but at the moment
I'm not groking the advantage of running these tools in a container.
Chris
On Sun, Dec 13, 2015 at 7:07 PM, Joe Brockmeier <j...@redhat.com> wrote:
> On 12/13/2015 07:11 PM, Chris Murphy wrote:
>> OK at this moment I'm thinking hdparm and smartmontools just need to
>> go on the ISO, along with iotop.
>
> What's the usage scenario you're pictur
On Fri, Dec 11, 2015 at 12:33 PM, Joe Brockmeier <j...@redhat.com> wrote:
> On 12/11/2015 02:23 PM, Chris Murphy wrote:
>>
>> These I have running in a fedora container. lspci mostly works, but
>> getting full -vvnn detail requires --privileged=true. And the other
loc failed
systemd-222-8.fc23.x86_64
I'd file a bug but I don't even know what to file it against. The full
journal output is here:
http://fpaste.org/3001
--
Chris Murphy
___
cloud mailing list
cloud@lists.fedoraproject.org
http://lists.fedoraproject
doesn't
help. I still can't login.
So is this a docker bug?
Chris Murphy
___
cloud mailing list
cloud@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org
On Sat, Dec 12, 2015 at 1:31 PM, Chris Murphy <li...@colorremedies.com> wrote:
> I have a lead.
>
> I'm still working on this bug:
> https://bugzilla.redhat.com/show_bug.cgi?id=1290691
>
>
> And when I do this:
> [root@f23a ~]# docker run --net=host --pid=host -v /d
On Thu, Dec 10, 2015 at 9:18 PM, Dusty Mabe <du...@dustymabe.com> wrote:
>
>
> On 12/10/2015 08:35 PM, Chris Murphy wrote:
>> Followup question: Does Docker directly use a thin pool without
>> creating (virtual size) logical volumes? Because I don't see any other
es --privileged=true. And the other
three require it. iotop additionally needs --net=host. I'd be OK with
them just being available in a container, but it might make more sense
to just include them in the atomic ISO installation, maybe even
borrowing a list from the Server product?
docker-pool
> LV for you and have the docker daemon use that as the backing store.
>
> Let me know if this is what you were looking for or not!
Yes.
--
Chris Murphy
___
cloud mailing list
cloud@lists.fedoraproject.org
http:/
tems like this:
[ 7818.790685] XFS (dm-4): Mounting V5 Filesystem
[ 7819.038211] XFS (dm-4): Ending clean mount
[ 7834.219132] XFS (dm-4): Unmounting Filesystem
So it's using XFS on something, that isn't appearing in mount on the
host or in the container. And multiple
On Tue, Dec 8, 2015 at 11:22 PM, Adam Williamson
<adamw...@fedoraproject.org> wrote:
> On Tue, 2015-12-08 at 11:26 -0700, Chris Murphy wrote:
>> On Mon, Dec 7, 2015 at 6:39 PM, Adam Williamson
>> <adamw...@fedoraproject.org> wrote:
>> > Hi folks! For those who a
rview?distri=fedora=23=23_Postrelease_20151209=1
>
> Click on the green dot and you see the individual test:
OOH - OK it's not at all obvious the dot is a link. Is it possible for
the test text itself having the link?
--
Chris Murphy
___
cloud mailing list
c
On Wed, Dec 9, 2015 at 2:02 PM, Joe Brockmeier <j...@redhat.com> wrote:
> On 12/09/2015 03:48 PM, Chris Murphy wrote:
>> Does anyone else think it'd be useful to
>> have the nightly atomic installer ISO listed at
>> https://apps.fedoraproject.org/releng-dash/ ? Or maybe
On Wed, Dec 9, 2015 at 3:44 PM, Chris Murphy <li...@colorremedies.com> wrote:
> On Wed, Dec 9, 2015 at 3:00 PM, Adam Williamson
> <adamw...@fedoraproject.org> wrote:
>
>> That's an overview page. The Logs & Assets tab is available for each
>> individual *test
=
So it might be that the Fedora 23 Atomic ISO behavior is the result of
upstream behavior, and Fedora 22 had a modifier that no longer exists
in Fedora 23?
--
Chris Murphy
___
cloud mailing list
cloud@lists.fedoraproject.org
http://lists.f
On Wed, Dec 9, 2015 at 3:47 PM, Chris Murphy <li...@colorremedies.com> wrote:
> On Wed, Dec 9, 2015 at 2:02 PM, Joe Brockmeier <j...@redhat.com> wrote:
>> On 12/09/2015 03:48 PM, Chris Murphy wrote:
>>> Does anyone else think it'd be useful to
>>> have
n useful.
If it fails the auto test, all that probably matters is the fail
summary. More likely is if it passes all auto tests to have a link to
the image so a manual test can try to blow it up, right?
--
Chris Murphy
___
cloud mailing list
cloud@lists.f
at a particular game in a particular location, not the
details of the hand they're dealt.
--
Chris Murphy
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
e
hardlink, punches through to the original file in a completely
different tree, affecting all trees, and is therefore not atomic. (On
Btrfs this duplication can be made efficient with reflinks instead of
hardlinks, but that's trivia.)
--
Chris Murphy
___
clo
100 matches
Mail list logo
