Separate Repository for Atomic Specific Fedora-Dockerfiles

[Trishna Guha]

Hi,

We have a repository on Github named Fedora-Dockerfiles [0]. The Repository
contains Dockerfiles but those are not **atomic** specific.
So adding ability to use **atomic** command will make **other hosts** lose
the ability to use the Dockerfiles.

Since we are focusing on having production ready Dockerfiles for Atomic
host, Should we create a separate repository that contains Atomic specific
Dockerfiles?


[0] https://github.com/fedora-cloud/Fedora-Dockerfiles


-- 
Regards,
Trishna Guha

[Josh Berkus]

On 09/07/2016 11:17 PM, Trishna Guha wrote:
>  Hi,
>  
>  We have a repository on Github named Fedora-Dockerfiles [0]. The
>  Repository contains Dockerfiles but those are not **atomic** specific.
>  So adding ability to use **atomic** command will make **other hosts**
>  lose the ability to use the Dockerfiles.
>  
>  Since we are focusing on having production ready Dockerfiles for Atomic
>  host, Should we create a separate repository that contains Atomic
>  specific Dockerfiles? 
In what way are images created for atomic not runnable on regular
Docker?  Examples?

-- 
--
Josh Berkus
Project Atomic
Red Hat OSAS

[Trishna Guha]

On Thu, Sep 8, 2016 at 8:10 PM, Josh Berkus <jberkus(a)redhat.com&gt; wrote:
>  In what way are images created for atomic not runnable on regular
>  Docker?  Examples?
>  
Sure.

[1] is the Dockerfile for running cockpit on atomic host. We can run the
container with *atomic* command.
[2] is the Dockerfile for redis container (regular). We can run the
container on all kind of host, even on atomic host but not with *atomic*
command.

[1]
https://github.com/fedora-cloud/Fedora-Dockerfiles/tree/master/cockpit-ws
[2] https://github.com/fedora-cloud/Fedora-Dockerfiles/tree/master/redis

-- 
Regards,
Trishna Guha

[Josh Berkus]

On 09/08/2016 10:33 AM, Trishna Guha wrote:
>  On Thu, Sep 8, 2016 at 8:10 PM, Josh Berkus <jberkus(a)redhat.com
>  <mailto:[e-mail]>> wrote:
> >
> > In what way are images created for atomic not runnable on regular
> > Docker?  Examples?
> >
>  Sure.
>  
>  [1] is the Dockerfile for running cockpit on atomic host. We can run the
>  container with *atomic* command. 
Sure, but you can also run this on regular Docker if you want.  You just
need to pass the right flags.

>  [2] is the Dockerfile for redis container (regular). We can run the
>  container on all kind of host, even on atomic host but not with *atomic*
>  command. 
But you can run it with "atomic" command, it just reverts to the basic
"docker run".


-- 
--
Josh Berkus
Project Atomic
Red Hat OSAS

[Micah Abbott]

On 09/08/2016 01:33 PM, Trishna Guha wrote:
>  On Thu, Sep 8, 2016 at 8:10 PM, Josh Berkus <jberkus(a)redhat.com
>  <mailto:[e-mail]>> wrote:
> >
> > In what way are images created for atomic not runnable on regular
> > Docker?  Examples?
> >
>  Sure.
>
>  [1] is the Dockerfile for running cockpit on atomic host. We can run the
>  container with *atomic* command. 
A little harder to do, but not impossible:

# cat /etc/os-release  | grep PRETTY_NAME
PRETTY_NAME="Fedora 24 (Cloud Edition)"

# dnf -y install cockpit-bridge
...

# docker pull cockpit/ws
...

# docker run -ti --rm --privileged -v /:/host cockpit/ws 
/container/atomic-install
+ sed -e /pam_selinux/d -e /pam_sepermit/d /etc/pam.d/cockpit
+ mkdir -p /host/etc/cockpit/ws-certs.d
+ chmod 755 /host/etc/cockpit/ws-certs.d
+ chown root:root /host/etc/cockpit/ws-certs.d
+ mkdir -p /host/var/lib/cockpit
+ chmod 775 /host/var/lib/cockpit
+ chown root:wheel /host/var/lib/cockpit
+ /bin/mount --bind /host/etc/cockpit /etc/cockpit
+ /usr/sbin/remotectl certificate --ensure

# docker run -d --privileged --pid=host -v /:/host cockpit/ws 
/container/atomic-run --local-ssh
5e66a6e21817a06b2b3b0080fca96c616d6bfa866d7d5b3e091cf460f1adc85b

# docker ps
CONTAINER ID        IMAGE               COMMAND                  CREATED 
             STATUS              PORTS
        NAMES
5e66a6e21817        cockpit/ws          "/container/atomic-ru"   5 
seconds ago       Up 4 seconds
        cranky_snyder

# curl http://localhost:9090
<!DOCTYPE html>
<html>
   <head>
     <script>
var environment = 
{"hostname":"localhost","os-release":{"CPE_NAME":"cpe:/o:fedoraproject:fedora:24","PRIVACY_POLICY_UR
L":"https://fedoraproject.org/wiki/Legal:PrivacyPolicy",&q...
ora","REDHAT_SUPPORT_PRODUCT_VERSION":"24","VARIANT":"Cloud

Edition","PRETTY_NAME":"Fedora 24 (Cloud Edition)","HOME_U
RL":"https://fedoraproject.org/","REDHAT_SUPPORT_PROD...
ON":"24","VERSION":"24 (Cloud 
Edition)","NAME":"Fedora","BUG_REPORT_URL&q...
0;34"}};
     </script>
     <title>Cockpit starting...</title>
...

> [2] is the Dockerfile for redis container (regular). We can run the
> container on all kind of host, even on atomic host but not with *atomic*
> command.
>
> [1]
> https://github.com/fedora-cloud/Fedora-Dockerfiles/tree/master/cockpit-ws
> [2] https://github.com/fedora-cloud/Fedora-Dockerfiles/tree/master/redis
>
> --
> Regards,
> Trishna Guha
>
>
>
> _______________________________________________
> cloud mailing list
> cloud(a)lists.fedoraproject.org
> https://lists.fedoraproject.org/admin/lists/[e-mail]
>

[Matthew Miller]

On Thu, Sep 08, 2016 at 11:47:35AM +0530, Trishna Guha wrote:
>  We have a repository on Github named Fedora-Dockerfiles [0]. The
> Repository
>  contains Dockerfiles but those are not **atomic** specific.
>  So adding ability to use **atomic** command will make **other hosts** lose
>  the ability to use the Dockerfiles. 
The Plan of Record is to move away from that repository and to a
dist-git style collection of repositories as part of
https://fedoraproject.org/wiki/Changes/Layered_Docker_Image_Build_Service
(possibly synced with github)?


-- 
Matthew Miller
<mattdm(a)fedoraproject.org&gt;
Fedora Project Leader

[Trishna Guha]

On Fri, Sep 9, 2016 at 9:17 PM, Matthew Miller <mattdm(a)fedoraproject.org&gt;
wrote:
>  The Plan of Record is to move away from that repository and to a
>  dist-git style collection of repositories as part of
>  https://fedoraproject.org/wiki/Changes/Layered_Docker_Image_Build_Service
>  (possibly synced with github)?
>  
+1
dist-git style collection of repositories synced with github is probably a
good idea.
We now have a ticket/meeting item to discuss what to do with that
repository [1].

Comments will be appreciated there.

[1] https://pagure.io/atomic-wg/issue/180.

-- 
Regards,
Trishna Guha

trishnaguha17(a)gmail.com
trishnag.wordpress.com