On 03/17/2016 04:28 AM, Dusty Mabe wrote:
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 wrote:
On 03/16/2016 10:47 AM,
python3-gobject-base is needed to use OSTree python bindings.
runc is a tool for spawning containers based on Open Container
Specifications.
Needed for: https://github.com/projectatomic/atomic/issues/298
Signed-off-by: Giuseppe Scrivano
---
fedora-atomic-docker-host.json
Okay, so removing resolv_conf and manage-resolv-conf removes the yaml
error from /var/log/boot.log
Where can I go to fix this issue / make project atomic more cloud-init
compliant? Seems like resolv_conf isn't implemented yet in this
cloud-init version?
On 03/16, Charlie Drage wrote:
> Seems
Seems that resolv doesn't work correctly. I'm getting an ambiguous
error within /var/boot/log, despite having valid yaml
My cloud-init:
#cloud-config
hostname: cloud
manage-resolv-conf: true
resolv_conf:
nameservers:
- "8.8.4.4"
- "8.8.8.8"
ssh_authorized_keys:
-
That would be great if you could!
On 03/17, Josh Berkus wrote:
> On 03/17/2016 08:32 AM, Charlie Drage wrote:
> > After a bit of Google-fu, would these be the best / better sources to
> > add to the community page?
> >
> > https://fedoraproject.org/wiki/Cloud_SIG
> >
> >
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 wrote:
> On 03/16/2016 10:47 AM, Dusty Mabe 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 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
Ah, that's the reason why, since resolv isn't on the module list it
isn't enabled by default on atomic hosts.
boot_cmd will be the solution for it then (for now)..
i'll contact the package maintainer, thanks matt!
On 03/16, Matt Micene wrote:
> Fedora Atomic doesn't modify the cloud-init
Hi all,
So I've found http://www.projectatomic.io/community/ where there is a
section for "How to join and help".
Unfortunatley the two links provided are for rpm-ostree and then a
goto link for https://wiki.centos.org/Cloud
Neither of which provide any information on how to start developing
--cap-add SYS_ADMIN ?
On 03/16, 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 trying to do it but I keep getting an error
>
> ```
> [vagrant@vanilla-f23atomic ~]$ rpm
On Thu, Mar 17, 2016, at 08:25 AM, Giuseppe Scrivano wrote:
> python3-gobject-base is needed to use OSTree python bindings.
>
> runc is a tool for spawning containers based on Open Container
> Specifications.
>
> Needed for: https://github.com/projectatomic/atomic/issues/298
Makes sense to me.
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 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
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
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 atomic host that has docker 1.10. I
want to have a
14 matches
Mail list logo