On Fri, Jun 1, 2018 at 10:14 AM, arnaud gaboury
wrote:
> So my idea is to "share" what I added in one machine (/etc settings and
> layered packages, let's call the machine "origin") to other machines
> (targeted VM) in an automatic way.
> It seems that articles about automate building atomic
Hi Arnaud,
On Thu, May 31, 2018 at 7:51 AM, arnaud gaboury
wrote:
> I decided to go Fedora Atomic and installed it on one VM. I have now the
> perfect setup for what I want and will now install Atomic with these setup
> to the other VM. What is the best way to clone my current machine and
>
On Wed, May 23, 2018 at 5:09 PM, Dusty Mabe wrote:
> Jonathan, Can you share how you copied the files from the ISO and also
> what your pxelinux.cfg is ?
Nothing too special. I mounted the install ISO and copied vmlinuz and initrd
in `images/pxeboot` to the PXE directory.
On Tue, May 15, 2018 at 3:51 PM, Chris Negus wrote:
> In the wake of James Mills' excellent article on replacing docker in Atomic
> (https://access.redhat.com/solutions/3414221), I realized we had missed
> documenting "rpm-ostree override" in the RHEL Atomic user docs. I'll
Hi Marius,
Thanks for the detailed report! If you don't mind, let's track this
upstream. I've opened [1] and copied your email in there.
Will investigate!
Thanks,
Jonathan
[1] https://github.com/projectatomic/rpm-ostree/issues/1250
On Wed, Feb 14, 2018 at 9:00 AM, Marius Vollmer
> > Any ideas on where I should open a bug? Anaconda?
>
> FYI - openqa shows the same result:
>
> https://openqa.fedoraproject.org/tests/127122#step/_do_install_and_reboot/32
I did some investigation and opened a bug against grub2 with
my findings:
> I think part of this depends on if the kernel modules need to be embedded
> in the initramfs. If not then normal package layering should work:
> `rpm-ostree install foo && reboot`.
That's correct.
>
> If so, I think it gets more complicated. Jonathan/Colin may be able to give
> you more info
Hi,
If I understand correctly, in its current state, F26 AH will
be shipping with the atomic package which added the
rpm-build deps. The update that removes it again is blocked
in testing:
https://bodhi.fedoraproject.org/updates/FEDORA-2017-ac1919a04b
Double-checking the current state:
$
I traced it down to:
http://pkgs.fedoraproject.org/cgit/rpms/atomic.git/commit/?h=f25=7d15e4a0be2db29deda4b92a039a041d81bbe205
http://pkgs.fedoraproject.org/cgit/rpms/atomic.git/commit/?h=f25=cb845639e7388bb9aa3b5aef7dabffa3434b1ae1
I.e. atomic needs to build RPMs for the system container
work.
Thanks, good catch! I think at the time I missed the fact
that Bodhi had just been turned on for F26. Anyway, update
submitted now:
https://bodhi.fedoraproject.org/updates/atomic-devmode-0.3.6-1.fc26
- Original Message -
> Downgraded:
> atomic-devmode 0.3.6-1.fc25 -> 0.3.5-2.fc26
>
>
The Docker docs also has a breakdown of incompatibilities:
https://docs.docker.com/engine/userguide/storagedriver/overlayfs-driver/#/overlayfs-compatibility
Notably, there's the open(2) issue that has already been
mentioned. The second issue is that rename(2) can fail if
trying to move a dir
Hi Chen,
You can customize an Atomic Host using cloud-init:
http://cloudinit.readthedocs.io/en/latest/
There's also a quickstart available on the Project Atomic
website to guide you through that process:
http://www.projectatomic.io/docs/quickstart/
Hope that helps!
- Original Message
- Original Message -
> My question is that will it be possible to install local rpm files via
> 'rpm-ostree pkg-add'?
Yeah, that's:
https://github.com/projectatomic/rpm-ostree/blob/master/TODO#L35
It shouldn't be too hard to add support for this (and we
should do that). A hacky
- Original Message -
> For instance, I bring up a two node, one master cluster w/ atomic
> fedora or centos, using the kube/contrib ansible, and then I run the
> projectatomic/guestbookgo-atomicapp, locate automatically-assigned
> NodePort for the guestbook (kubectl describe service
> I'm not sure what the answer to this is; I'm reluctant to recommend
> installing a whole suite of diagnostic tools just for the case of a
> bare-metal user who has a problem. But on the other hand, the current
> situation isn't really vialble for bare-metal users either.
There is now `ostree
- Original Message -
> On 06/22/2016 11:36 AM, Muayyad AlSadi wrote:
> > What about developer mode in grub menu?
>
> The grub entry won't be added as part of a rebase.
Right, if you don't currently have a grub entry, rebasing
will not make one appear.
However, the grub entry should be
> Any solution for testing that needs to involve a reboot?
Check out `unlock --hotfix`! It will make the overlayfs
persistent across reboots.
https://github.com/ostreedev/ostree/blob/master/man/ostree-admin-unlock.xml#L74
- Original Message -
> Any way to mount /usr/lib to read-write?
Yup! You can just do:
mount -o remount,rw /usr
> I can't seem to find the fstab entry for /usr nor my
> google-fu helps.
It's a bind mount that happens on boot right before switch
root (see [1]).
> Seems that centos
That should probably be doable, yes. Would you mind filing
an issue upstream[1] to have a place to discuss?
Just wondering, if you don't have a VGA console, how do you
select the Developer Mode boot option? Can that be done over
serial as well with the default GRUB config?
[1]
- Original Message -
> On 02/01/2016 09:05 PM, Colin Walters wrote:
> > On Fri, Jan 29, 2016, at 11:08 AM, Jonathan Lebon wrote:
> >> Make atomic-devmode part of the tree compose.
> >
> > Not sure if you saw, there was some FESCo disc
Make atomic-devmode part of the tree compose. Note that I did not yet
add the related packages in order to enable the plymouth splash screen.
I'd like first to see if it's possible to minimize the package to only
include graphics we need.
---
fedora-atomic-docker-host.json | 3 ++-
1 file
Just uploaded a newer image (available at [1]) which
addresses some of the feedback received:
- The generated passwords should now be easier to type,
with no easily misidentified letters.
- Helper message to explicitly say how to log into
Cockpit.
- New tmux terminals and
> Is there a specific reason it has to be a boot option in the standard
> image rather than offering a separate developer mode image?
I think the primary reason is simplicity, and not having to change
the release pipeline much. Also knowing that you're playing with
exactly the same bits as you
- Original Message -
> That may have worked. I can now see the org's repos from
> the github2fedmsg app, but it gives an error message when
> enabling any of them. Will troubleshoot it more with RJ
> tomorrow (CC'ed), the author of github2fedmsg.
OK, this is set up now for
- Original Message -
> I discovered a group for this may already exist as:
>
> https://github.com/orgs/projectatomic/teams/build-service-admins-committers
>
> I just added you; does that work?
That may have worked. I can now see the org's repos from
the github2fedmsg app, but it gives
25 matches
Mail list logo