Re: [atomic-devel] atomic install/run cockpit does not work on atomic-ws

2018-03-29 Thread Muayyad AlSadi
Then it's might be a good time to have detas for ws.


On Thu, Mar 29, 2018, 6:39 PM Micah Abbott  wrote:

> On 03/29/2018 12:34 PM, Muayyad AlSadi wrote:
> >  > rpm-ostree upgrade --check
> >
> > it gives me,
> >
> > mporting metadata [=] 100%
> > **
> >
> ERROR:src/app/rpmostree-dbus-helpers.c:1362:rpmostree_print_cached_update:
> > assertion failed: (g_variant_dict_lookup (, "ref-has-new-commit",
> > "b", _new_checksum))
> > Aborted (core dumped)
>
> This looks like:
>
> https://github.com/projectatomic/rpm-ostree/issues/1267
>
> You can work around it like so:
>
> "In the meantime, you can work around this by setting
> AutomaticUpdatePolicy in /etc/rpm-ostreed.conf to check (see
> rpm-ostreed.conf(5)). If you don't have the timer running, no checks
> will actually be performed in the background."
>
>
> > while "rpm-ostree upgrade" works fine, but I guess it's too much ~200MB,
> > we are supposed to get deltas aren't we?
>
> We have deltas for Fedora Atomic Host, but not for Atomic Workstation.
>
>
> > 466 metadata, 663 content objects fetched; 191,364 KiB transferred in
> > 163 seconds
> > Checking out tree e703ce3... done
> >
> >
> >
> >
> > On Tue, Mar 27, 2018 at 3:59 PM, Matthias Clasen  > > wrote:
> >
> >
> > what is the command line that check for updates without applying
> > the update? and list pending updates?
> > is it pull?
> >
> >
> > rpm-ostree upgrade --check
> >
> >
> >
> > when an update came to atomic ws, it removed those (picture
> > inlined, look at removals: 10 packages)
> >
> > is there a way to carry those newly installed packages from the
> > current layer into the updae?
> >
> > rpm-ostree has all needed information to do this.
> >
> > it knows they were added in the past
> > it knows they are still missing in the update
> > it knows how to merge (or rebase) them
> >
> >
> > rpm-ostree upgrade does that - it keeps the exiting layer in place.
> >
> >
>


Re: [atomic-devel] atomic install/run cockpit does not work on atomic-ws

2018-03-29 Thread Micah Abbott

On 03/29/2018 12:34 PM, Muayyad AlSadi wrote:

 > rpm-ostree upgrade --check

it gives me,

mporting metadata [=] 100%
**
ERROR:src/app/rpmostree-dbus-helpers.c:1362:rpmostree_print_cached_update: 
assertion failed: (g_variant_dict_lookup (, "ref-has-new-commit", 
"b", _new_checksum))

Aborted (core dumped)


This looks like:

https://github.com/projectatomic/rpm-ostree/issues/1267

You can work around it like so:

"In the meantime, you can work around this by setting 
AutomaticUpdatePolicy in /etc/rpm-ostreed.conf to check (see 
rpm-ostreed.conf(5)). If you don't have the timer running, no checks 
will actually be performed in the background."



while "rpm-ostree upgrade" works fine, but I guess it's too much ~200MB, 
we are supposed to get deltas aren't we?


We have deltas for Fedora Atomic Host, but not for Atomic Workstation.


466 metadata, 663 content objects fetched; 191,364 KiB transferred in 
163 seconds

Checking out tree e703ce3... done




On Tue, Mar 27, 2018 at 3:59 PM, Matthias Clasen > wrote:



what is the command line that check for updates without applying
the update? and list pending updates?
is it pull?


rpm-ostree upgrade --check



when an update came to atomic ws, it removed those (picture
inlined, look at removals: 10 packages)

is there a way to carry those newly installed packages from the
current layer into the updae?

rpm-ostree has all needed information to do this.

it knows they were added in the past
it knows they are still missing in the update
it knows how to merge (or rebase) them


rpm-ostree upgrade does that - it keeps the exiting layer in place.






Re: [atomic-devel] atomic install/run cockpit does not work on atomic-ws

2018-03-29 Thread Muayyad AlSadi
> rpm-ostree upgrade --check

it gives me,

mporting metadata [=] 100%
**
ERROR:src/app/rpmostree-dbus-helpers.c:1362:rpmostree_print_cached_update:
assertion failed: (g_variant_dict_lookup (, "ref-has-new-commit", "b",
_new_checksum))
Aborted (core dumped)

while "rpm-ostree upgrade" works fine, but I guess it's too much ~200MB, we
are supposed to get deltas aren't we?

466 metadata, 663 content objects fetched; 191,364 KiB transferred in 163
seconds
Checking out tree e703ce3... done




On Tue, Mar 27, 2018 at 3:59 PM, Matthias Clasen  wrote:

>
> what is the command line that check for updates without applying the
>> update? and list pending updates?
>> is it pull?
>>
>
> rpm-ostree upgrade --check
>
>
>>
>> when an update came to atomic ws, it removed those (picture inlined, look
>> at removals: 10 packages)
>>
>> is there a way to carry those newly installed packages from the current
>> layer into the updae?
>>
>> rpm-ostree has all needed information to do this.
>>
>> it knows they were added in the past
>> it knows they are still missing in the update
>> it knows how to merge (or rebase) them
>>
>>
> rpm-ostree upgrade does that - it keeps the exiting layer in place.
>


Re: [atomic-devel] atomic install/run cockpit does not work on atomic-ws

2018-03-27 Thread Matthias Clasen
> what is the command line that check for updates without applying the
> update? and list pending updates?
> is it pull?
>

rpm-ostree upgrade --check


>
> when an update came to atomic ws, it removed those (picture inlined, look
> at removals: 10 packages)
>
> is there a way to carry those newly installed packages from the current
> layer into the updae?
>
> rpm-ostree has all needed information to do this.
>
> it knows they were added in the past
> it knows they are still missing in the update
> it knows how to merge (or rebase) them
>
>
rpm-ostree upgrade does that - it keeps the exiting layer in place.


Re: [atomic-devel] atomic install/run cockpit does not work on atomic-ws

2018-03-23 Thread Muayyad AlSadi
I've installed them using

[root@localhost ~]# rpm-ostree install htop cockpit-bridge cockpit-system
cockpit-docker cockpit-networkmanager cockpit-ostree
[root@localhost ~]# rpm-ostree ex livefs
[root@localhost ~]# rpm-ostree ex livefs --replace

then run cockpit with

[root@localhost ~]# sytemctl start docker
[root@localhost ~]# sytemctl start sshd
[root@localhost ~]# atomic install registry.fedoraproject.org/f27/cockpit
[root@localhost ~]# atomic run --name cockpit
registry.fedoraproject.org/f27/cockpit

and it worked

> cockpit has been more for managing servers I think so the needed bits
aren't embedded in FAW.

I believe its bridge should be added (the same way we have sshd
pre-installed) to have consistent experience
because the proper way to add more applications to atomic is via flatpak or
docker/atomic
but cockpit won't work neither ways.

I have some questions

what is the command line that check for updates without applying the
update? and list pending updates?
is it pull?


when an update came to atomic ws, it removed those (picture inlined, look
at removals: 10 packages)

is there a way to carry those newly installed packages from the current
layer into the updae?

rpm-ostree has all needed information to do this.

it knows they were added in the past
it knows they are still missing in the update
it knows how to merge (or rebase) them



​



On Fri, Mar 23, 2018 at 7:34 PM, Dusty Mabe  wrote:

>
>
> On 03/23/2018 11:56 AM, Muayyad AlSadi wrote:
> > hi,
> >
> > I've installed the latest atomic workstation on a vm
> >
> > I tried to run cockpit by typing
> >
> > atomic install registry.fedoraproject.org/f27/cockpit  fedoraproject.org/f27/cockpit>
> >
> > but it gives
> >
> > cockpit-bridge must be installed on host
> >
> >
> >
> > is there a way to run cockpit on atomic workstation?
>
>
> cockpit has been more for managing servers I think so the needed bits
> aren't embedded in FAW.
>
> If you want you can layer in the same packages we include in FAH. They are
> listed here:
>
> https://pagure.io/fedora-atomic/blob/master/f/fedora-
> atomic-host.json#_112-116
>
>
> >
> > BTW: I wrote a review in Arabic for atomic-ws, it's awesome. I'll
> translate it very soon. but I would like to include cockpit in the english
> version
> >
> > http://g0alkeeper.blogspot.com/2018/03/blog-post.html
>
> Nice! Thanks for helping us reach another audience!
>
> Dusty
>


Re: [atomic-devel] atomic install/run cockpit does not work on atomic-ws

2018-03-23 Thread Dusty Mabe


On 03/23/2018 11:56 AM, Muayyad AlSadi wrote:
> hi,
> 
> I've installed the latest atomic workstation on a vm
> 
> I tried to run cockpit by typing
> 
> atomic install registry.fedoraproject.org/f27/cockpit 
> 
> 
> but it gives
> 
> cockpit-bridge must be installed on host
>
>
> 
> is there a way to run cockpit on atomic workstation?


cockpit has been more for managing servers I think so the needed bits aren't 
embedded in FAW.

If you want you can layer in the same packages we include in FAH. They are 
listed here:

https://pagure.io/fedora-atomic/blob/master/f/fedora-atomic-host.json#_112-116


> 
> BTW: I wrote a review in Arabic for atomic-ws, it's awesome. I'll translate 
> it very soon. but I would like to include cockpit in the english version
> 
> http://g0alkeeper.blogspot.com/2018/03/blog-post.html

Nice! Thanks for helping us reach another audience!

Dusty 



[atomic-devel] atomic install/run cockpit does not work on atomic-ws

2018-03-23 Thread Muayyad AlSadi
hi,

I've installed the latest atomic workstation on a vm

I tried to run cockpit by typing

atomic install registry.fedoraproject.org/f27/cockpit

but it gives

cockpit-bridge must be installed on host

is there a way to run cockpit on atomic workstation?

BTW: I wrote a review in Arabic for atomic-ws, it's awesome. I'll translate
it very soon. but I would like to include cockpit in the english version

http://g0alkeeper.blogspot.com/2018/03/blog-post.html