[atomic-wg] Issue #175 `Fedora 24 atomic image Fedora-Atomic-24-20161025.0.x86_64.qcow is not allowing ssh`

kushal added a new comment to an issue you are following: `` The following bug seems to be the problem. https://bugzilla.redhat.com/show_bug.cgi?id=1212082#c21 `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/175

Re: Docker Layered Image Naming and Tagging

On Fri, Oct 21, 2016 at 11:10 AM, Matthew Miller wrote: > On Fri, Oct 21, 2016 at 10:06:41AM -0500, Adam Miller wrote: >> For layered images, we would follow something similar to: >> >> registry.fedoraproject.org/fedora/24/httpd:latest >>

Re: [atomic-devel] Announcing Fedora Atomic "latest" download URLs

On Fri, Sep 30, 2016 at 11:57 AM, Josh Berkus wrote: > On 09/30/2016 08:58 AM, Adam Miller wrote: >> On Thu, Sep 29, 2016 at 1:54 PM, Josh Berkus wrote: >>> On 09/29/2016 08:18 AM, Adam Miller wrote: On behalf of the Fedora Cloud Working Group, I

[atomic-wg] Issue #175 `Fedora 24 atomic image Fedora-Atomic-24-20161025.0.x86_64.qcow is not allowing ssh`

dustymabe added a new comment to an issue you are following: `` actually I don't think it shut itself down now. looks like the gssproxy service fails to come up and has to time out before other things can continue during boot: ``` -bash-4.3# systemctl status gssproxy.service ●

[atomic-wg] Issue #175 `Fedora 24 atomic image Fedora-Atomic-24-20161025.0.x86_64.qcow is not allowing ssh`

dustymabe added a new comment to an issue you are following: `` Looks like the instance is shutting itself down: https://paste.fedoraproject.org/460804/14774076 `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/175

Deploy Containers, Containerized Application on Atomic host with Ansible

Hi, The purpose is to make Fedora atomic host production ready. I have been working with containers on Atomic host a lot. The idea is to automate docker build, run process for docker image and containers on atomic host, this is where Ansible comes in to play. There is also an interesting tool

[atomic-wg] Issue #175 `Fedora 24 atomic image Fedora-Atomic-24-20161025.0.x86_64.qcow is not allowing ssh`

kushal added a new comment to an issue you are following: `` Note: strangely the vagrant libvirt is also failing for me with ssh issues.

[atomic-wg] Issue #175 `Fedora 24 atomic image Fedora-Atomic-24-20161025.0.x86_64.qcow is not allowing ssh`

kushal reported a new issue against the project: `atomic-wg` that you are following: `` Even though autocloud managed to ssh, when I tried to ssh into an instance on our OpenStack, it never allowed a connection. Opening this ticket to dig more into this. *