November 2017 - Atomic Working Group (ARCHIVED)

[atomic-wg] Issue #339: Adding Fedora to AWS Marketplace
by David Duncan 21 Nov '18

21 Nov '18

davdunc reported a new issue against the project: `atomic-wg` that you are following: `` I have made arrangements with Mattdm to host Marketplace AMIs of F27 in the AWS Marketplace. These will be hosted by me as a member of the Fedora community. This allows us to get around certain legal issues that have heretofore prevented the images hosting. * Need Fedora Marketing to assist with writeup for the listing. * TODO F27 submission prior to release date (there is a security audit) Account number for Marketplace deployment is 662243699625. This is legally separate from the FAS managed account. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/339

3 8

[atomic-wg] Issue #354: help.md file for each container
by Petr Hracek 08 Jun '18

08 Jun '18

phracek reported a new issue against the project: `atomic-wg` that you are following: `` I thinks each container should provide to user some help page. Fedora has requirement for providing such file https://fedoraproject.org/wiki/Container:Guidelines#Help_File The help.md file should contain some required fields like: - image name - maintainer - name - description - usage - if container uses environment variables then section ENVIRONMENT VARIABLES - if container exposes ports then also section SECURITY IMPLICATION e.g. memcached help.md ~~~ % MEMCACHED(1) Container Image Pages % Petr Hracek % February 6, 2017 # NAME memcached - Memcached is a high-performance, distributed memory object caching system # DESCRIPTION Memcached is a high-performance, distributed memory object caching system, generic in nature, but intended for use in speeding up dynamic web applications by alleviating database load. The container itself consists of: - fedora/f26 base image - memcached RPM package Files added to the container during docker build include: /files/memcached.sh # USAGE To get the memcached container image on your local system, run the following: docker pull docker.io/modularitycontainers/memcached # ENVIRONMENT VARIABLES The image recognizes the following environment variables that you can set during initialization be passing `-e VAR=VALUE` to the Docker run command. | Variable name | Description | | :----------------------- | ----------------------------------------------------------- | | `MEMCACHED_DEBUG_MODE` | Increases verbosity for server and client. Parameter is -vv | | `MEMCACHED_CACHE_SIZE` | Sets the size of RAM to use for item storage (in megabytes) | | `MEMCACHED_CONNECTIONS` | The max simultaneous connections; default is 1024 | | `MEMCACHED_THREADS` | Sets number of threads to use to process incoming requests | # SECURITY IMPLICATIONS Lists of security-related attributes that are opened to the host. -p 11211:11211 Opens container port 11211 and maps it to the same port on the host. # SEE ALSO Memcached page <https://memcached.org/> ~~~ `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/354

8 36

[atomic-wg] Issue #364: Article for F27: Running Fedora images on Microsoft Azure
by Dusty Mabe 29 May '18

29 May '18

dustymabe reported a new issue against the project: `atomic-wg` that you are following: `` We have done some work to get our images booting properly on MSFT azure. Brent has volunteered to write a blog post (draft [here](https://gist.github.com/baude/cc8fccc51eacfc0964cd14afc202df5c)) We'll try to publish this on fed mag. I'll work with fedmag team to get this published. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/364

4 7

[atomic-wg] Issue #375: Article for F27: The new Atomic Workstation
by Josh Berkus 28 May '18

28 May '18

jberkus reported a new issue against the project: `atomic-wg` that you are following: `` Since we're now offering regular updates for Atomic Workstation, it's time for a detailed blog post about installing it and running it. Maybe even a series. Ideal would be a summary article in Fedora Magazine, and a detailed series over time on the Atomic blog. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/375

6 9

[atomic-wg] Issue #366: Blog post covering AWS MP availability for F27
by David Duncan 28 May '18

28 May '18

davdunc reported a new issue against the project: `atomic-wg` that you are following: `` blog post announcing the availability of F27 Atomic in the AWS Marketplace. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/366

4 4

[atomic-wg] Issue #331: Issue Tracker for F27 release blockers
by Dusty Mabe 28 May '18

28 May '18

dustymabe reported a new issue against the project: `atomic-wg` that you are following: `` This ticket will be used throughout the f27 release to track potential blocker bugs and/or important bugs for the next release. A blocker bug is a bug that we will choose not to release on if it is not fixed. An important bug is a bug that we want fixed but may choose not to block on. **Blocker Bugs** - [BZ#1490505](https://bugzilla.redhat.com/show_bug.cgi?id=1490505) cloud-init fails when calling `xfs_growfs /dev/mapper/atomicos-root` on Fedora Atomic Host **Important Bugs** Over time only the description of this bug will be edited for updates. The comments of this bug will be used like a *changelog* for the description. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/331

3 13

[atomic-wg] Issue #355: Article For F27: Migrating Kubernetes
by Josh Berkus 28 May '18

28 May '18

jberkus reported a new issue against the project: `atomic-wg` that you are following: `` We need an article on how to migrate from built-in kubernetes to system container kubernetes when migrating from F26 to F27. This is our most critical article for the release. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/355

5 12

[atomic-wg] Issue #386: Provide updated examples for composing custom ostrees
by Micah Abbott 13 Apr '18

13 Apr '18

miabbott reported a new issue against the project: `atomic-wg` that you are following: `` We've received requests/complaints from #atomic on Freenode about the lack of up to date documentation for composing custom ostrees. ``` I've been trying to build my own atomic repo using rpm-ostree for the past couple days. I'm using a Fedora 27 workstation to build a repo for Atomic Fedora 27. I've tried adapting multiple instructions found online (most of them very old). Do working instructions exist anywhere for Fedora 27 Atomic? ``` It seems like we could benefit from an updated version of @jasonbrooks blog post for Fedora 27: https://www.projectatomic.io/blog/2014/11/build-your-own-atomic-updates/ And perhaps another edition that covers composing your own F27 Workstation ostree? `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/386

3 8

[atomic-wg] Issue #374: go-md2man deployed in osbs can't render tables
by Tomas Tomecek 15 Mar '18

15 Mar '18

ttomecek reported a new issue against the project: `atomic-wg` that you are following: `` Hi, I just tried to build my container image and let osbs generate the `help.1` file. It worked! The only problem I have is that the present version deployed inside infrastructure does not support rendering tables. Which means that this help.md page ``` % tools (1) Container Image Pages % Tomas Tomecek % September 11th, 2017 # NAME tools - container with all the management tools you miss in Atomic Host # DESCRIPTION You find plenty of well-known tools within this container. Here comes the full list: | Package | Summary | Executables | | --------------- | ------------------------------------------------------------------------------------------- | ---------------------------------- | | bash-completion | Programmable completion for Bash | | | bc | GNU's bc (a numeric processing language) and dc (a calculator) | /usr/bin/bc | | | | /usr/bin/dc | | bind-utils | Utilities for querying DNS name servers | /usr/bin/arpaname | ``` is translated to ``` tools (1) September 11th, 2017 tools (1) NAME tools - container with all the management tools you miss in Atomic Host DESCRIPTION You find plenty of well-known tools within this container. Here comes the full list: USAGE You should invoke this container using atomic command: $ atomic run f26/tools ``` (yes, the table is missing) when it should be translated to ``` tools (1) September 11th, 2017 tools (1) NAME tools - container with all the management tools you miss in Atomic Host DESCRIPTION You find plenty of well-known tools within this container. Here comes the full list: ┌────────────────┬────────────────────────────────────────────┬────────────────────────────────────┐ │Package │ Summary │ Executables │ ├────────────────┼────────────────────────────────────────────┼────────────────────────────────────┤ │bash-completion │ Programmable completion for Bash │ │ ├────────────────┼────────────────────────────────────────────┼────────────────────────────────────┤ │bc │ GNU's bc (a numeric processing language) │ /usr/bin/bc │ │ │ and dc (a calculator) │ │ ├────────────────┼────────────────────────────────────────────┼────────────────────────────────────┤ │ │ │ /usr/bin/dc │ ├────────────────┼────────────────────────────────────────────┼────────────────────────────────────┤ │bind-utils │ Utilities for querying DNS name servers │ /usr/bin/arpaname │ ``` I used `golang-github-cpuguy83-go-md2man-1.0.7-1.fc28.x86_64` to do that. Would be awesome to have that version deployed. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/374

5 24

[atomic-wg] Issue #379: Identify users for docker hub auto builds for system containers
by Steve Milner 21 Feb '18

21 Feb '18

smilner reported a new issue against the project: `atomic-wg` that you are following: `` As part of the work to start github->docker hub autobuilds for system containers we will need a GitHub which will give link to a docker hub account. Are there specific accounts already available which would make sense to reuse? Do we need to create accounts specific to auto building for both GitHub and docker hub? I tend to believe we should avoid a specific human account tied to this but instead use a service account. Reference: https://docs.docker.com/docker-hub/builds/ `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/379

3 8

2025

2024

2023

2022

2021

2020

2019

2018

2017

Atomic Working Group (ARCHIVED) November 2017