On Fri, Apr 03, 2015 at 12:34:38AM -0500, Scott Collier wrote:
> I was testing cockpit on the F22 Atomic image and ran into this issue.
> Cockpit would start, but I could not connect to it because SSH was having a
> problem. The error cockpit gave after trying to login to the web interface
> was:
I tried to test the UID/GID stuff last night with a rebase from Fedora 22
to CentOS7. I started with Fedora 22 atomic at [1]. I had to do a workaround
for some hostname issue (see [2]). When it rain I got an error:
-bash-4.3# rpm-ostree status
TIMESTAMP (UTC) VERSION ID OS
I tried to use the CentOS image [1] tonight. I noticed several issues
that may be known but I didn't see them in http://bugzilla.centos.org.
1 - I had to use 'runcon -r system_r -t install_t rpm-ostree upgrade'
see the bug for Fedora at [2]. I think you guys already know about
this
2 - I
On Thu, May 14, 2015 at 11:42:37PM -0400, Dusty Mabe wrote:
>
> I tried to use the CentOS image [1] tonight. I noticed several issues
> that may be known but I didn't see them in http://bugzilla.centos.org.
>
> 1 - I had to use 'runcon -r system_r -t install_t rpm-ostr
On Thu, May 14, 2015 at 11:27:16PM -0400, Dusty Mabe wrote:
>
> I tried to test the UID/GID stuff last night with a rebase from Fedora 22
> to CentOS7. I started with Fedora 22 atomic at [1]. I had to do a workaround
> for some hostname issue (see [2]). When it rain I got an error:
&g
On Thu, May 21, 2015 at 04:22:58PM -0400, Tim St Clair wrote:
> Every reboot it's ignored.
>
> Only on an explicit deamon-reload did it take the unit file into account.
>
> -Tim
>
Unlikely since the daemon-reload picked it up, but is there any chance
the selinux context on the files got mess
I have a situation where rpm-ostree gets confused on which remote it should be
using. If register a system using subscription manager and then rebase it onto
some other tree, then perform an upgrade the system is totally confused about
what remote it should be using. The version of rpm-ostree I
On Thu, May 28, 2015 at 10:16:29AM -0400, Dusty Mabe wrote:
>
> Basically the problem is that the remote should be *lab*, but is
> *rhel-atomic-host-ostree*.
I opened https://bugzilla.redhat.com/show_bug.cgi?id=1226007 for this.
On Mon, Jun 01, 2015 at 11:41:38AM -0500, JJ Asghar wrote:
>
> Hey everyone!
>
> As part of our one of our hack days at Chef, we decided that we should
> automate the installation/bootstrap of ProjectAtomic[1]. Fair warning, it???s
> not production ready by any standard, so please take a look b
Hey all,
Sorry for the wide distribution.. We'd like to promote the joint test
day we are doing next week for Atomic. Please see Jason's blog post for
more details and join us on the test day:
http://www.projectatomic.io/blog/2015/09/combined-fedora-centos-atomic-test-day-next-week/
- Dusty
I thought this might be of interest. I am going to paste the whole
thing here so people can comment in-line if they want. This is just a
report of information and doesn't necessarily indicate any problems.
Unique packages in CentOS7/Fedora 23 Atomic:
< = CENTOS
> = FEDORA
> audit
< aud
Hi,
In the container-tools team we have been having discussions about the
lifecycle of an atomicapp. We have essentially decided that there are
more verbs that we want to use than those that are defined in the Generic
Labels [1]. Vasek has proposed an idea [2] that I think would be useful
for a
On Wed, Oct 07, 2015 at 01:11:15PM -0400, Colin Walters wrote:
> On Wed, Oct 7, 2015, at 12:24 PM, Dusty Mabe wrote:
>
> > The idea is more or less to support an application developer being
> > able to define his/her own verbs to allow the user to call from atomic
> > CLI
On 10/08/2015 05:53 AM, Daniel J Walsh wrote:
On 10/07/2015 12:22 PM, Colin Walters wrote:
Hi,
On Fri, Aug 14, 2015, at 05:45 PM, Daniel J Walsh wrote:
Yes although I don't want to transfer, since I still want my
rhatdan/docker. But we could create a docker fork on atomic.
I noticed http
On 10/10/2015 06:57 AM, Daniel J Walsh wrote:
On 10/07/2015 12:24 PM, Dusty Mabe wrote:
Hi,
In the container-tools team we have been having discussions about the
lifecycle of an atomicapp. We have essentially decided that there are
more verbs that we want to use than those that are defined
On 10/11/2015 07:29 AM, Daniel J Walsh wrote:
On 10/10/2015 09:03 AM, Dusty Mabe wrote:
On 10/10/2015 06:57 AM, Daniel J Walsh wrote:
On 10/07/2015 12:24 PM, Dusty Mabe wrote:
Hi,
In the container-tools team we have been having discussions about the
lifecycle of an atomicapp. We have
On 10/16/2015 07:32 AM, Tobias Florek wrote:
What's the minimum amount of they py2 stack we'd need to support Ansible?
Well, minimum is hard to tell, because you can always use ansible's raw
module, which does not need python at all. What modules do we consider
as minimum.
I ran
# git grep -
On 11/12/2015 05:17 PM, Michael McGrath wrote:
On Thu, Nov 12, 2015 at 3:53 PM, Amanda Carter wrote:
Adding the list. Both questions still open.
IMHO https://bugzilla.redhat.com/show_bug.cgi?id=1276775 is a blocker
https://bugzilla.redhat.com/show_bug.cgi?id=1278984 not a blocker if
it can
On 11/12/2015 05:37 PM, Dusty Mabe wrote:
On 11/12/2015 05:17 PM, Michael McGrath wrote:
On Thu, Nov 12, 2015 at 3:53 PM, Amanda Carter
wrote:
Adding the list. Both questions still open.
IMHO https://bugzilla.redhat.com/show_bug.cgi?id=1276775 is a blocker
https://bugzilla.redhat.com
Please test and add karma:
https://bodhi.fedoraproject.org/updates/FEDORA-2015-b26290fd1e
On 11/10/2015 11:18 AM, Charlie Drage wrote:
Hi all,
The problem that we have at the moment is most of our testing scripts
/ tools are located on personal Github user accounts. The context
being atomicapp as well as the eclipse CDK integrations being on
personal accounts.. Rather than searchin
On 11/13/2015 11:40 AM, Daniel J Walsh wrote:
On 11/12/2015 06:19 PM, Dusty Mabe wrote:
Hey All,
We've been having conversations recently about the current
architecture of Atomicapp and the way we have envisioned people using
it. I prepared a presentation for a meeting we had today
On 11/19/2015 04:47 PM, Amanda Carter wrote:
- Original Message -
From: "Amanda Carter"
To: "Michael McGrath"
Cc: "Matthew Miller" , atomic-devel@projectatomic.io, "Colin Walters"
, "Dusty
Mabe" , "Adam Miller"
Sent:
I have had a few discussions with Dan and with the Atomic App core
team over the past few weeks. We have recognized some changes that we
can make to Atomic App to make the integration go easier. Below is one
proposed change:
- atomicapp will now manage instances of applications in a similar
mann
In fedora the 1.9 docker rpm is out. I am having issues pushing to the
repo.
If I push like I used to be able to:
```
[root@f23 helloapache (master *=)]# docker push dustymabe/helloapache
The push refers to a repository [dustymabe/helloapache] (len: 1)
unable to ping registry endpoint https://d
On 12/03/2015 08:34 AM, Daniel J Walsh wrote:
Lokesh what is the current state of docker for Fedora 23, 22? >
Dan, Should I open a BZ for this?
On 12/04/2015 12:56 AM, Brian (bex) Exelbierd wrote:
On Nov 23, 2015, at 8:17 PM, Daniel J Walsh wrote: >> >> On 11/22/2015 11:09 AM, Brian (bex) Exelbierd wrote: >>> >>> 2)
Could argument parsing in Atomic CLI be made more flexible than the
current OPT system? Could the parser learn how to
I am getting an error when trying to rebase to the updates-testing
ostree. It is a similar fsetxattr error we have seen in the past:
# Go to known reproducer starting point:
-bash-4.3# rpm-ostree deploy 23.54 && reboot
# After reboot:
-bash-4.3# rpm-ostree rebase
fedora-atomic:fedora-atomic/f2
On 02/16/2016 12:27 PM, Giuseppe Scrivano wrote:
> Dusty Mabe writes:
>
>> I am getting an error when trying to rebase to the updates-testing
>> ostree. It is a similar fsetxattr error we have seen in the past:
>>
>>
>> # Go to known reproducer starting po
On 03/03/2016 10:06 AM, Daniel J Walsh wrote:
>
>
> On 03/03/2016 10:04 AM, Jan Pazdziora wrote:
>> Hello,
>>
>> I have container images where the INSTALL phase can be interactive,
>> asking questions, and also passwords.
>>
>> For that, it would make sense to define INSTALL as
>>
>> docke
I typically don't have a VGA console attached to my VMs when testing. Could
we have developer mode support automatic login over serial console (ttyS0) as
well?
Dusty
On 03/10/2016 12:38 PM, Jonathan Lebon wrote:
> That should probably be doable, yes. Would you mind filing
> an issue upstream[1] to have a place to discuss?
Yep, here ya go: https://github.com/jlebon/atomic-devmode/issues/2
>
> Just wondering, if you don't have a VGA console, how do you
> sel
On 03/16/2016 10:51 AM, Daniel J Walsh wrote:
>
>
> On 03/16/2016 10:47 AM, Dusty Mabe wrote:
>> I am using the updates-testing f23 atomic host that has docker 1.10. I
>> want to have a shared mount between the host and a docker container.
>>
>> I'm tryin
On 03/16/2016 12:02 PM, Daniel J Walsh wrote:
>
>
> On 03/16/2016 11:42 AM, Dusty Mabe wrote:
>>
>> On 03/16/2016 10:51 AM, Daniel J Walsh wrote:
>>>
>>> On 03/16/2016 10:47 AM, Dusty Mabe wrote:
>>>> I am using the updates-testing f23 atom
I am using the updates-testing f23 atomic host that has docker 1.10. I
want to have a shared mount between the host and a docker container.
I'm trying to do it but I keep getting an error
```
[vagrant@vanilla-f23atomic ~]$ rpm -q docker
docker-1.10.2-6.git0f5ac89.fc23.x86_64
[vagrant@vanilla-f23
On 03/16/2016 01:15 PM, Daniel J Walsh wrote:
>
>
> On 03/16/2016 12:35 PM, Dusty Mabe wrote:
>>
>> On 03/16/2016 12:02 PM, Daniel J Walsh wrote:
>>>
>>> On 03/16/2016 11:42 AM, Dusty Mabe wrote:
>>>> On 03/16/2016 10:51 AM, Daniel J Walsh wr
On 03/28/2016 10:39 AM, Colin Walters wrote:
> One of the goals I have for Atomic Host is that we are doing more integration
> testing work than the traditional client-side package assembly model.
>
> However, in order to achieve that goal, we need to enable developers to
> quickly and rapidly
On 03/30/2016 07:14 PM, Josh Berkus wrote:
> On 03/30/2016 01:06 PM, Matthew Miller wrote:
>> On Mon, Mar 28, 2016 at 07:59:04PM -0400, Jonathan Lebon wrote:
Any solution for testing that needs to involve a reboot?
>>> Check out `unlock --hotfix`! It will make the overlayfs
>>> persistent ac
On 03/31/2016 12:09 PM, Daniel J Walsh wrote:
>
>
> On 03/31/2016 11:58 AM, Dusty Mabe wrote:
>>
>> On 03/30/2016 07:14 PM, Josh Berkus wrote:
>>> On 03/30/2016 01:06 PM, Matthew Miller wrote:
>>>> On Mon, Mar 28, 2016 at 07:59:04PM -0400, Jonathan Le
On 03/31/2016 12:21 PM, Matthew Miller wrote:
> On Thu, Mar 31, 2016 at 12:09:16PM -0400, Daniel J Walsh wrote:
>> On 03/31/2016 11:58 AM, Dusty Mabe wrote:
>>> I'm down to write a blog post for this. You will have to fight over
>>> where it gets posted (projectat
https://github.com/ansible/ansible-modules-extras/pull/1902
See link. I thought there might be some interested parties on this list :)
If I `ostree admin unlock --hotfix` a clean clone is created for me to rollback
to. That
is pretty awesome. The only thing I don't like is that it's not too clear from
a call to
`rpm-ostree status` that the deployment I'm on is "dirty". Would it be
reasonable to open
an issue to request some m
I've noticed we switched up the path to the ref for Fedora 24 vs Fedora 23
atomic.
https://dl.fedoraproject.org/pub/fedora/linux/atomic/23/refs/heads/fedora-atomic/f23/
https://dl.fedoraproject.org/pub/fedora/linux/atomic/24/refs/heads/fedora-atomic/24/
Was this intentional?
Please test this docker update so that we can get it in to F24. Right now
docker in stable is broken:
https://bodhi.fedoraproject.org/updates/FEDORA-2016-3223384190
Hey All,
As far as I can tell Docker is broken in F24 atomic. We have had
issues with docker for a while now but testing on fedora cloud base
from the updates-testing repo seemed to show the problem as resolved.
However, now that docker-1.10.3-7.gita41254f.fc24.x86_64 is in stable
we now see tha
On 05/11/2016 02:40 PM, Antonio Murdaca wrote:
> upgrading oci-register-machine made this working again (it was related to
> this https://bugzilla.redhat.com/show_bug.cgi?id=1328961)
indeed. I was able to workaround by doing:
ostree admin unlock --hotfix
curl -O
https://kojipkgs.fedoraproject
Need testing for new selinux so we can fix the final Atomic Host bug
for F24 [1]. The karma needs to be applied at [2].
To test on F24 atomic host today you can do:
ostree admin unlock --hotfix
curl -O
https://kojipkgs.fedoraproject.org//packages/selinux-policy/3.13.1/185.fc24/noarch/selinux
Good work everyone! We are almost there. Only need 1 more +1 and this
update might make it into stable today!
Now who is going to step up to the plate? :)
Dusty
On 05/12/2016 09:16 PM, Dusty Mabe wrote:
>
> Need testing for new selinux so we can fix the final Atomic Host bug
> f
On 05/13/2016 06:50 AM, Dusty Mabe wrote:
>
> Good work everyone! We are almost there. Only need 1 more +1 and this
> update might make it into stable today!
>
> Now who is going to step up to the plate? :)
>
Turns out it was runcom :) - This update has enough karma now
On 05/02/2016 11:13 AM, Micah Abbott wrote:
> On 04/29/2016 08:06 PM, Dusty Mabe wrote:
>> If I `ostree admin unlock --hotfix` a clean clone is created for me to
>> rollback to. That
>> is pretty awesome. The only thing I don't like is that it's not too clear
&
On 06/21/2016 12:21 PM, Adam Miller wrote:
> Hello all,
Hey Adam,
> The original schedule for today's Fedora Two-Week Atomic Release
> was going to include a cut-over of our back end Release Infrastructure
> and AutoCloud automated QA environment to be compose based (one of the
> building b
On 08/09/2016 06:39 PM, nore...@fedoraproject.org wrote:
>
> A new update of Fedora Cloud Atomic Host has been released and can be
> downloaded at:
>
> Images can be found here:
>
> https://getfedora.org/en/cloud/download/atomic.html
>
> Respective signed CHECKSUM files can be found here:
On 08/17/2016 10:23 AM, Vasiliy Tolstov wrote:
> I'm try to install atomic on baremetal server via atomic host iso
> (from fedora) but installer says that it can't install bootloader.
> My setup
> raid1 from sda1 and sdb1 for /boot
> raid1 from sda2 and sdb2 for / (lvm)
>
> As i see data present
omic to baremetal?
>
> 2016-08-18 0:20 GMT+03:00 Vasiliy Tolstov :
>> 2016-08-17 18:21 GMT+03:00 Dusty Mabe :
>>> What is the state of the system when you start? What exactly is anaconda
>>> telling you? Are you using a kickstart file? Are you doing a UEFI boot or
>>
We need to add mdadm to Fedora Atomic Host so that we can support software raid
disk setups.
https://pagure.io/fedora-atomic/pull-request/8
On 08/18/2016 05:53 AM, Vasiliy Tolstov wrote:
> 2016-08-18 10:34 GMT+03:00 Vasiliy Tolstov :
>> 2016-08-18 8:04 GMT+03:00 Dusty Mabe :
>>> I believe I am able to recreate this issue. Will try to investigate some
>>> more tomorrow.
>>
>>
>> Tha
On 08/18/2016 01:47 PM, Daniel J Walsh wrote:
>
>
> On 08/18/2016 12:00 PM, Dusty Mabe wrote:
>> We need to add mdadm to Fedora Atomic Host so that we can support software
>> raid disk setups.
>>
>> https://pagure.io/fedora-atomic/pull-request/8
>>
Adding fedora cloud list.
On 08/22/2016 10:13 AM, Colin Walters wrote:
> Hi, I'd like to propose a fairly fundamental rework of Atomic Host. TL;DR:
>
> - Move towards "system containers" (or layered packages) for flannel/etcd
> - Move towards containers (system, or Docker) for kubernetes-maste
Adding atomic-devel
On 08/23/2016 10:09 PM, Dusty Mabe wrote:
> The atomic ISO images are using the wrong tree. The images built on
> 8/23 [1] yield the following system after an install:
>
> -bash-4.3# rpm-ostree status
> TIMESTAMP (UTC) VERSION ID
On 08/22/2016 07:03 AM, Vasiliy Tolstov wrote:
> 2016-08-18 19:29 GMT+03:00 Dusty Mabe :
>> So here is something that is close. Anaconda seems to require things
>> be on a partition.
>>
>> part raid.01 --size=1 --grow --ondisk=sda
>> part raid.02 --size=1
Adding rel-eng. They might be able to help us out more on this topic.
Dusty
On 08/23/2016 10:09 PM, Dusty Mabe wrote:
> The atomic ISO images are using the wrong tree. The images built on
> 8/23 [1] yield the following system after an install:
>
> -bash-4.3# rpm-ostree status
&
On 08/23/2016 11:30 PM, nore...@fedoraproject.org wrote:
>
> A new update of Fedora Cloud Atomic Host has been released and can be
> downloaded at:
>
> Images can be found here:
>
> https://getfedora.org/en/cloud/download/atomic.html
>
> Respective signed CHECKSUM files can be found here:
lease?)
Dusty
[1]
https://download.fedoraproject.org/pub/alt/atomic/stable/Atomic/x86_64/iso/Fedora-Atomic-dvd-x86_64-24-20160820.0.iso
>
>> On 08/23/2016 10:09 PM, Dusty Mabe wrote:
>>> The atomic ISO images are using the wrong tree. The images built on
>>> 8/23 [1
On 08/25/2016 12:05 PM, Dusty Mabe wrote:
>
>
> On 08/25/2016 04:07 AM, Peter Robinson wrote:
>>> Adding rel-eng. They might be able to help us out more on this topic.
>>
>> Could you maybe add a little bit more information? Like what tree is
>> expected to
On 08/29/2016 02:29 PM, Vasiliy Tolstov wrote:
> i'm build ostree using fedora and my own copr repos.
> But resulted tree have only official fedora repos, does it possible to
> add copr repo when building not using treecompose-post script?
>
If you don't want to create the file in the post scri
In Fedora 25 I grabbed the new kernel with overlayfs support [1] and I
configured docker to run with overlayfs by using
DOCKER_STORAGE_OPTIONS="--storage-driver=overlay2"
in /etc/sysconfig/docker-storage.
[1]
https://kojipkgs.fedoraproject.org//packages/kernel/4.8.0/0.rc5.git4.1.fc25/x86_64/k
Latest F25 Vagrant box:
https://kojipkgs.fedoraproject.org//work/tasks/7256/16027256/Fedora-Atomic-Vagrant-25-20161010.n.0.x86_64.vagrant-libvirt.box
```
-bash-4.3# rpm-ostree status
State: idle
Deployments:
● fedora-atomic:fedora-atomic/25/x86_64/docker-host
Version: 25.22 (2016-10-10 10:
https://bodhi.fedoraproject.org/updates/FEDORA-2016-0ed0314ad7
We need karma on this package so we can get new docker-storage-setup to take
care of https://bugzilla.redhat.com/show_bug.cgi?id=1387934.
Dusty
Hey all,
In Fedora Atomic the release process is disjoint from the rest of
Fedora in that our images aren't produced as part of the normal
"production" composes and RCs.
I will make it a point to send out an email like this on the same day
that every RC is created in Fedora so that we can attempt
If no one opposes I will help Giuseppe set up the repos for hosting his
system containers [1] on docker hub under our organization. We'll be
doing this tomorrow.
Dusty
[1]
https://lists.projectatomic.io/projectatomic-archives/atomic-devel/2016-November/msg00015.html
dwalsh sent a message to the devel list about this. Follow along/respond here:
https://lists.fedoraproject.org/archives/list/de...@lists.fedoraproject.org/message/JBUEITVRLFHHOPQXSSFVYL5WQA3754ZZ/
On 11/25/2016 07:15 PM, Vasiliy Tolstov wrote:
> I'm try to update my atomic host from fedora 24 to fedora 25.
> And my network fails to up. Please see attached screenshot.
> systemd-networkd.service: Failed at step NAMESPACE spawning
> /usr/lib/systemd/systemd-networkd: Too many levels of symbol
On 11/28/2016 10:00 AM, Vasiliy Tolstov wrote:
> 2016-11-28 17:55 GMT+03:00 Dusty Mabe :
>> Hey Vasiliy. By default we use NetworkManager in Atomic Host. Are you
>> enabling systemd-networkd? Can you share how your machine is set up?
>
>
> I found hack in pagure.io, an
The Vagrant Atlas page with the new atomic host:
https://atlas.hashicorp.com/fedora/boxes/
https://atlas.hashicorp.com/fedora/boxes/25-atomic-host/versions/20161207
vagrant init fedora/25-atomic-host; vagrant up
or, if you already have the box, to get the new one:
vagrant box update --box fedor
After I get a bug[1] fixed and out the door I'm going to publish
a blog post/docs on setting up Fedora 25 Atomic host and/or Cloud
base to use overlay2 as the storage driver for docker.
I'd like for everyone that can to test this out and to start running
their container workloads with overlay2 w
On 12/12/2016 05:13 PM, Josh Berkus wrote:
> On 12/12/2016 02:12 PM, Dusty Mabe wrote:
>>
>> After I get a bug[1] fixed and out the door I'm going to publish
>> a blog post/docs on setting up Fedora 25 Atomic host and/or Cloud
>> base to use overlay2 as the stor
On 12/12/2016 05:19 PM, Jason Brooks wrote:
> On Mon, Dec 12, 2016 at 2:12 PM, Dusty Mabe wrote:
>>
>> After I get a bug[1] fixed and out the door I'm going to publish
>> a blog post/docs on setting up Fedora 25 Atomic host and/or Cloud
>> base to use overlay2
On 12/12/2016 05:12 PM, Dusty Mabe wrote:
>
> After I get a bug[1] fixed and out the door I'm going to publish
> a blog post/docs on setting up Fedora 25 Atomic host and/or Cloud
> base to use overlay2 as the storage driver for docker.
>
> I'd like for everyone t
On 12/12/2016 05:41 PM, Jason Brooks wrote:
> On Mon, Dec 12, 2016 at 2:24 PM, Dusty Mabe wrote:
>>
>>
>> On 12/12/2016 05:19 PM, Jason Brooks wrote:
>>> On Mon, Dec 12, 2016 at 2:12 PM, Dusty Mabe wrote:
>>>>
>>>> After I get a bug[1] f
On 12/12/2016 05:12 PM, Dusty Mabe wrote:
>
> After I get a bug[1] fixed and out the door I'm going to publish
> a blog post/docs on setting up Fedora 25 Atomic host and/or Cloud
> base to use overlay2 as the storage driver for docker.
>
> I'd like for everyone t
On 12/13/2016 01:02 PM, Colin Walters wrote:
> On Tue, Dec 13, 2016, at 12:45 PM, Clayton Coleman wrote:
>> Are the POSIX issues in applications running on overlay mostly resolved now?
>> I.e. if we flipped the default would be reasonably able to support a
>> diverse range of Linux workloads w
On 12/14/2016 07:51 AM, Daniel J Walsh wrote:
>
> I have heard that the issue with yum/rpm is being worked on in the kernel.
> For those that to not know the issue is for programs that open a file twice
> once for readonly and then later for read/write. In the first open the file
> is
> on the
On 12/22/2016 04:18 PM, nore...@fedoraproject.org wrote:
>
> A new update of Fedora Cloud Atomic Host has been released and can be
> downloaded at:
>
> Images can be found here:
>
> https://getfedora.org/en/cloud/download/atomic.html
>
> Respective signed CHECKSUM files can be found here:
This is affecting the stable version of docker and thus is affecting atomic
host
(i.e. if you pull containers from gcr.io you can't run kubernetes.)
docker is not properly pulling gcr.io images
https://bugzilla.redhat.com/show_bug.cgi?id=1409873
We need this to fix docker pull from gcr.io bug which causes us to not be able
to run kubernetes:
https://bodhi.fedoraproject.org/updates/docker-1.12.5-4.git03508cc.fc25
This bug that this fixes is here:
https://bugzilla.redhat.com/show_bug.cgi?id=1409873
On 01/05/2017 07:16 PM, Josh Berkus wrote:
> So, I've done some testing, thanks to Dusty's setup.
>
> I wasn't able to test on Kubernetes because of some setup issues.
> However, I hammered away at Docker using some IO-intensive applications,
> including PostgreSQL and Etcd, both of which write
On 01/06/2017 06:16 PM, nore...@fedoraproject.org wrote:
>
> A new update of Fedora Cloud Atomic Host has been released and can be
> downloaded at:
>
> Images can be found here:
>
> https://getfedora.org/en/cloud/download/atomic.html
>
> Respective signed CHECKSUM files can be found here:
for configuring linux bridges.
https://pagure.io/fedora-atomic/pull-request/46
On 01/11/2017 11:27 AM, Jerry Zhang wrote:
> As we are moving forward with the system container effort,
> I would like to add the images to the projectatomic docker hub,
> so users can directly pull with the atomic cli as opposed
> to building the images from source. Effectively, the images
> wou
https://bodhi.fedoraproject.org/updates/FEDORA-2017-dbc2b618eb
On 01/12/2017 08:40 AM, Matthew Miller wrote:
> On Wed, Jan 11, 2017 at 11:11:42PM -0500, Dusty Mabe wrote:
>> https://bodhi.fedoraproject.org/updates/FEDORA-2017-dbc2b618eb
>
> Also, I will buy a beer or package of cookies or whatever other
> necessary bribe for anyone who c
On 01/13/2017 09:45 AM, Daniel J Walsh wrote:
>
>
> On 01/13/2017 08:38 AM, Antonio Murdaca wrote:
>> Hi,
>>
>> Seems like no people are really using docker-latest in Fedora. I
>> realized that because the version in F25 is old and nobody adds karma
>> to the updates in bodhi there. Is there a
I noticed today when comparing two trees, one from Dec25 and the
latest one, that the version of cockpit went backwards.
!cockpit-bridge-126-1.fc25.x86_64
=cockpit-bridge-120-1.fc25.x86_64
!cockpit-docker-126-1.fc25.x86_64
=cockpit-docker-120-1.fc25.x86_64
!cockpit-networkmanager-126-1.fc25.noarc
On 01/13/2017 11:18 AM, Antonio Murdaca wrote:
>
>
>
> That sounds good. However, I didn't fully understand how to achieve that. Do
> you mean that docker-latest shouldn't build docker-latest anymore but just
> require "docker" and make a symlink out of it?
Exactly. in other words, it's ju
On 01/14/2017 10:09 AM, Muayyad AlSadi wrote:
> Hi,
>
> I have a kube spec like this (full yaml here
> https://paste.fedoraproject.org/527041/48440635/raw/)
>
> ...
> spec:
> containers:
> - name: mypod
> image: fedora
> imagePullPolicy: Always
>
We are going to try to release our 2WA release on Tuesday (tomorrow).
The automated tests are passing but feel free to test out today's build
and see if there are any issues!
The cloud images are here:
https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-25-20170116.0/compose/CloudIma
On 01/15/2017 04:47 PM, Antonio Murdaca wrote:
>
>
> On Jan 15, 2017 10:07 PM, "Dusty Mabe" <mailto:du...@dustymabe.com>> wrote:
>
>
>
> On 01/13/2017 11:18 AM, Antonio Murdaca wrote:
> >
> >
> >
> > Tha
On 01/15/2017 04:08 PM, Dusty Mabe wrote:
>
>
> I'm seeing the same thing. Will have to investigate further to get to
> the bottom of it.
>
Hey Muayyad,
So this is a problem with kubernetes in fedora. You have two options
as a workaround for now:
- run the following co
On 01/16/2017 04:34 PM, Dusty Mabe wrote:
>
>
> On 01/15/2017 04:08 PM, Dusty Mabe wrote:
>>
>>
>> I'm seeing the same thing. Will have to investigate further to get to
>> the bottom of it.
>>
>
> Hey Muayyad,
>
> So this is a proble
There are a few bugs that are blocking 2wk release.
- one with the kernel that causes kube dns to not work
* https://bugzilla.redhat.com/show_bug.cgi?id=1414068
- one with kube that causes selinux breakage
* https://bugzilla.redhat.com/show_bug.cgi?id=1414096
We need to get these resolve
1 - 100 of 405 matches
Mail list logo
