Skip to content
This repository has been archived by the owner on Feb 24, 2020. It is now read-only.

*: package rkt for Debian #1307

Closed
3 tasks done
jonboulle opened this issue Aug 19, 2015 · 31 comments
Closed
3 tasks done

*: package rkt for Debian #1307

jonboulle opened this issue Aug 19, 2015 · 31 comments

Comments

@jonboulle
Copy link
Contributor

Ticket to track the progress of rkt being packaged for Debian.

This will not be performed by the rkt team, but this issue should track any work that needs to happen to unblock packaging.

Upstream Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782441

TODO:

have tagged releases for dependencies

@deucalion
Copy link

I know this is an external bug, but would it be possibe to re-open this bug and close it once it reached Debian/Ubuntu (i.e. the bug there was closed)? Thank you!

@jonboulle
Copy link
Contributor Author

@deucalion that's exactly the idea, this issue will remain open until rkt is packaged for Debian.

@iaguis
Copy link
Member

iaguis commented Sep 17, 2015

For ubuntu/debian systems that don't mount cgroup controllers individually in /sys/fs/cgroup the rkt package should depend on cgroup-lite. For example, on Ubuntu Utopic as showed in #1320 (comment)

@jonboulle
Copy link
Contributor Author

FWIW looks like there's a new maintainer: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782441#26
Perhaps we should reach out?

@alban
Copy link
Member

alban commented Nov 7, 2015

@onlyjob you are the new maintainer, aren't you? Welcome here!

@onlyjob
Copy link

onlyjob commented Nov 8, 2015

Thanks for warm welcome, Alban. :)

@jonboulle
Copy link
Contributor Author

Cross referencing from #1594 (comment):

we are not allowed to ship binary blobs and there is no way we can build coreos image from source. There are also incompatibilities with coreos image (e.g. "hello" example does not work due to lack of some library in CoreOS stage1 image, as far as I can tell). Finally stage1 image should be built at the same time when the package is built and from existing packages. Everything builds from native repository for security and build reproducibility hence downloading during build is not possible. Also policy prohibits shipping any source-less content as well as all binaries has to be (re-)built. I'm not going further into details but as you can see there are not only technical but also legal and policy reasons.

It should be possible to build/use "rkt" without any binary blobs. OS packages is a stable and predictable source for compilation of stage1 image, isn't it? All packages are available on build time.

@iaguis iaguis modified the milestones: v1+, v1.0.0 Jan 26, 2016
@chancez
Copy link
Contributor

chancez commented Feb 3, 2016

I was looking around to see the status of this. It looks like @onlyjob got rkt 0.8 building, and has something started: https://anonscm.debian.org/cgit/pkg-go/packages/rkt.git/

It looks like getting it updated shouldn't be too hard, especially with all the improvements made to stage1's and the build system.

@onlyjob
Copy link

onlyjob commented Feb 3, 2016

As usual time and funding are the issues. Package builds and works but ~20 dependency packages to be introduced to Debian in order to upload rkt. I'm struggling to allocate time for that and so far nobody volunteered to help...

@philips
Copy link
Contributor

philips commented Feb 3, 2016

@onlyjob What sort of funding issues?

Also, I reached out to a few debian developers I know who might be able to help. I will let you know.

@onlyjob
Copy link

onlyjob commented Feb 4, 2016

What sort of funding issues?

I work faster if effort is paid for... If some company interested to help introducing rkt to Debian they can help by sponsoring this work... None of my clients are funding packaging rkt...

@onlyjob
Copy link

onlyjob commented Mar 26, 2016

rkt is vendoring unreleased snapshot of appc/cni so it looks like the latter needs a release bump...

@onlyjob
Copy link

onlyjob commented Apr 1, 2016

Only one dependency is blocking rkt -- https://github.com/appc/cni;
All other dependencies were successfully accepted. :)

@philips
Copy link
Contributor

philips commented Apr 15, 2016

I believe this is fixed! http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782441

@onlyjob
Copy link

onlyjob commented Apr 15, 2016

rkt was indeed accepted to Debian so this is fixed.

https://packages.qa.debian.org/r/rkt.html

Thanks for all your help, guys. :)

@ghost
Copy link

ghost commented Apr 17, 2016

Good news!

What about Ubuntu?..

@onlyjob
Copy link

onlyjob commented Apr 17, 2016

What about Ubuntu?

Soon enough Ubuntu will leech rkt from Debian, just like they routinely leech almost all Debian packages...

I recommend to stay away from Ubuntu and use Debian.

@ghost
Copy link

ghost commented Apr 17, 2016

Soon enough Ubuntu will leech rkt from Debian, just like they routinely leech almost all Debian packages...

Okay, I hope, it will be available soon after Xenial release..

I recommend to stay away from Ubuntu and use Debian.

Why?.. Both systems looks stable (I compare Ubuntu Xenial LTS [which will will see in 1-2 weeks] with Debian), 5 years support - both systems...

My choice of Ubuntu mostly related with new versions of packages and kernel and recommendation from projects like Couchbase (in past were 2 main versions - RedHat and Ubuntu) or Openstack ( http://docs.openstack.org/ here they have installation guide for RedHat and Ubuntu, but not for Debian)... Also Microsoft going to integrate Ubuntu (not Debian) to Windows 10... Also Ubuntu is more popular system than Debian - it's more easy to get help about installing anything to it...

Anyway they both are nice systems...

@onlyjob
Copy link

onlyjob commented Apr 17, 2016

Why avoid Ubuntu? Because using derivative takes you further away from source of knowledge and introduce delays to propagation of fixes. Ubuntu is just about 2000 supported packages when Debian have more than 50_000. Almost everything Ubuntu pulls from Debian is doomed to rot without bugs being forwarded to Debian or even answered by someone who knows how to deal with the problem. With Ubuntu you'll be waiting for most packages to be fixed in Debian simply because Debian have more manpower. Ubuntu have history of introducing disruptive and incompatible changes (e.g. upstart) and break things that are working in Debian. Ubuntu is known for occasionally pulling experimental (i.e. not suitable for release) packages from Debian. Ubuntu releases on schedule which is harmful practice in software development.

Ubuntu adds additional restrictions on top of permissive licenses and uses controversial contributor's agreement. Ubuntu have corporate agenda and ultimately it exists to tie users into services that provide financial benefit to Canonical. I suppose one of my biggest concerns is that as much as Ubuntu needs to share their improvements with Debian they also need to withheld some "added value" in order to justify Ubuntu's very existence. Unfortunately unlike pure blends and decent Debian derivatives like Grml that have good technical justification and niche, Ubuntu is harmful because it divides community of Debian users and creates needless fragmentation. Debian is more trustworthy because it is community governed. I could continue with more arguments...

@lorddaedra, your preferred choice of Ubuntu is most likely based on ignorance rather than on understanding differences between Debian and Ubuntu. You might find it interesting that Debian have backports suite with newer packages;
I don't know situation with Couchbase but generally speaking one should be careful whenever vendor packages are involved. Openstack is quite active in Debian. To me what Microsoft is going to do is largely irrelevant - why should it affect my choice of operating system?
As for using popularity polls(?) for decision making you should be careful with that kind of reasoning as Windows is still somewhat more popular than Ubuntu therefore following your logic you should not be using Ubuntu because more popular OS is available... Knowledge and common sense are far more powerful for reasoning than blindly following the crowd...

@ghost
Copy link

ghost commented Apr 17, 2016

I like Debian too, it was my first or second linux (first was AltLinux on desktop) 9 years ago. I think, I mostly like Linux itself than any of Linux-based OS..

I just would like to install system with latest kernel and latest Rkt / Openstack... All other things will be inside containers...

So main thing that matter for me: speed of getting new updates: I would like to use latest kernel and software. If something goes wrong, I can reinstall it all. (It's okay if server will unavailable during maintenance every night for 2-3 hours, together with backups and IPMI support from motherboard it give me ability to use latest stable versions of all software without any problem, I can even automate it with Salt Stack).

According to Mark Shuttleworth, founder of Canonical, Ubuntu's parent company, 55 percent of OpenStack operating systems are on Ubuntu... (I do not need Openstack for now, but I would like to play with OpenStack+Ironic+network filesystems+CoreOS+Kubernetes+... after I will have more than 3 servers for cloud...)

For now I just would like to have latest kernel versions and latest Rkt and all software put to containers and run them via systemd service files & Rkt.

But not sure about kernel: usually I used Ubuntu because of newer kernel versions, it marked as stable, in Debian they are exists too (may be) but marked as unstable (so no one help me if I will find bug, they all will say: hey, you are using beta-versions, what else do you expect?..)...

I see main difference as: Centos and Debian for people who prefer stable and old software, Fedora and Ubuntu for people who prefer update system every day...

@onlyjob
Copy link

onlyjob commented Apr 17, 2016

On Debian you can always install newer kernel from official backports. Alternatively you can use "testing" suite if "stable" is too old for you. Linux kernel is very well maintained in Debian.

For (actively maintained) OpenStack on Debian see the following pages:

@lorddaedra, did you read what I've said about derivatives? CentOS is a derivative with all the problems I've mentioned. Main difference between CentOS and Ubuntu is that CentOS aims to be as much RHEL as possible without much ambitions while Ubuntu copy Debian and change it dramatically (break it) as well as claim that Ubuntu is somewhat "better" which is simply not true for almost every aspect of "betterness".

It is no use to say "Debian is for stable and old software". What do you think we are doing here? Packaging "old and stable" rkt? Besides there are different Debian suites -- "stable", "testing" and "unstable" as well as "jessie-backports" and "oldstable". Chose one that suites you best.

@ghost
Copy link

ghost commented Apr 18, 2016

@onlyjob, I partially agree with you. Not all things related with Ubuntu are good.. For example, I think, systemd is really nice system, much better than sysvinit or upstart... And Ubuntu was latest distro who started to use systemd... (I thought to switch to Fedora if Ubuntu will stay with upstart...) I prefer to use best components, but in this case Ubuntu was too slow ...

In other things I like Ubuntu steps, their vision. For example, I like Ubuntu as desktop OS, I like Unity, user experience on Ubuntu for me as user most close to Mac OS X user experience, I think, it's good. And I think, Ubuntu is better than Debian as desktop system because of Unity. I like systems like Gnome 3 or Unity, they looks modern.

People from debian IRC channel says, Debian testing channel is not for server usage. They suggested stable + backports...

But in case of, for example, Openstack https://qa.debian.org/developer.php?login=openstack-devel@lists.alioth.debian.org new packages not available for stable channel in Debian, but available in Ubuntu. [Not problem for me now - I think, I will try to play with Openstack by Mirantis, I feel it will be better than installing Openstack by Canonical/RedHat/Novell....]

For now with single server I feel, every OS will works fine. Because of I need only few packages - may be Salt Stack (for deployment containers, from official Salt Stack repository), Rkt (for running containers) and Postgres (may be I will pack it too, may be not - but anyway from official PostgreSQL repository), latest Docker (from official Docker repository) latest kernel and systemd and nothing more...

As you see, from list of packages, which versions are matter for me, only Rkt and Linux will be installed from OS repositories... And I feel after some weeks, CoreOS founders will start to support official Rkt repositories for all popular OSes to make new Rkt available for all Linux-based OSes in day of release on Git. It looks logical, all companies and communities do the same...

So for me it's more question about Ubuntu kernel version and settings vs Debian kernel version and settings...

@ghost
Copy link

ghost commented Apr 18, 2016

It is no use to say "Debian is for stable and old software". What do you think we are doing here? Packaging "old and stable" rkt?

It looks funny, but yes. If you will send Rkt packages to OS repositories then at the end after some years or months you will see big difference between Rkt version on github and Rkt version in OS repository...

To fix that companies usually provide their own official repositories. It require additional time&money but I feel, CoreOS will pay for that - if Rkt will be popular app - it will increase interest to CoreOS and their services at the end and they will earn more money, so this additional expenses looks as good investments.

@alban
Copy link
Member

alban commented Apr 18, 2016

rkt was indeed accepted to Debian so this is fixed.

@onlyjob thanks for the work! Should this issue be closed, or is there anything else to track here?

What about Ubuntu?..

@lorddaedra I believe nobody has started the work for packaging rkt on Ubuntu. Feel free to open a new issue to track the status. I'm happy to help packagers from all distros to package rkt.

I would also like to have some distro-specific documentation on https://github.com/coreos/rkt/blob/master/Documentation/distributions.md. It has some doc about some distributions but nothing about Debian or Ubuntu yet. PRs for this welcome :)

@onlyjob
Copy link

onlyjob commented Apr 18, 2016

@alban, please close this bug. We're done here! :) :)

@lorddaedra, I just want to add that nice interface is not worth having 97% unsupported packages on your system. Besides Unity is a matter of taste and some find it distasteful... I'm tired of reasoning with you and clearly you do not understand benefits and added value of software provided from native Debian repositories. One of the great things about Debian is that it is the best source of software you may need. Vendor package repositories are by definition inferior without distro quality control, continuous integration, security support, policy compliance, etc. Once packaging is ready the natural (and the best) thing to do is to work with distribution maintainers to ship software through official distro repositories. Vendor repositories have many problems that are not specific to particular software but rather to approach in general. Anyway I have no intention to contribute more to this discussion. Cheers.

@alban alban closed this as completed Apr 18, 2016
@onlyjob
Copy link

onlyjob commented Apr 18, 2016

Thanks! :)

@jonboulle jonboulle modified the milestones: v1.5.0, v1+ Apr 18, 2016
@ghost
Copy link

ghost commented Apr 20, 2016

@onlyjob,

having 97% unsupported packages on your system

Please, confirm I correctly understand your point of view. Do you say about packages from ubuntu repositories or about packages, which were installed by default during standard Ubuntu install?...

@onlyjob
Copy link

onlyjob commented Apr 20, 2016

@lorddaedra, I've said that about repositories of course. I don't know what percentage of unsupported packages installed by default...

@yuvipanda
Copy link

May I suggest that there are plenty of other places to have a discussion
about the relative merits of Linux distributions, and this ticket should be
allowed to rest in peace :)
On Apr 20, 2016 2:37 PM, "Dmitry Smirnov" notifications@github.com wrote:

@lorddaedra https://github.com/lorddaedra, I've said that about
repositories of course. I don't know what percentage of unsupported
packages installed by default...


You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#1307 (comment)

@onlyjob
Copy link

onlyjob commented Apr 20, 2016

You are certainly right, @yuvipanda. Sorry about that. Over and out. :)

@ghost
Copy link

ghost commented Apr 21, 2016

Okay :-) Thank you for discussion. :-)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

8 participants