News for hackers. Stuff that matters.
Re:Fedora 33 by kawsper on Wednesday October 28, 2020 @09:22AM (#24918412)
For anyone using Docker and thinking of trying out Fedora, here is a warning:

Fedora uses cgroupsv2 to push things forward, but no Docker release supports it yet, it's in master[0], but there are no release in sight as there is no ETA.

[0] https://github.com/moby/moby/pull/40174

Re:Fedora 33 by amarshall on Wednesday October 28, 2020 @09:31AM (#24918511)
As an alternative, Podman works well, but some features may be missing. It does, however, allow running containers rootless and remove the need for a daemon.

https://podman.io

Re:Fedora 33 by TrueDuality on Wednesday October 28, 2020 @10:56AM (#24919444)
I've made the switch entirely over to podman and haven't actually found any features to be missing besides docker-compose support, but their k8s style pods more or less have solved that for me.

There is only one 'gotcha' that I've hit, when building images specifically for AWS's ECR or Docker Hub, you need to add the flag `--format=docker` to your build step. Quay and a few others don't have this issue.

Re:Fedora 33 by amarshall on Wednesday October 28, 2020 @11:56AM (#24920282)
There is podman-compose, but it is most definitely missing features vs. docker-compose (as in whole subcommands are absent). I cannot remember what (if any) missing podman features remain, but I do run into occasional bugs and regressions with certain functionality.

Curious you mention needing `--format=docker`; I’ve pushed images to Docker Hub without doing that without issue.

https://github.com/containers/podman-compose

Re:Fedora 33 by TrueDuality on Wednesday October 28, 2020 @05:04PM (#24924131)
You'll be able to successfully push the images without it. Tags you pushed won't properly show up in docker hub and clients will have issues pulling not just the tags but the layers.

It's been a hot minute since I hit that issue, but I kind of doubt docker hub fixed it. I suspect fixing issues around OCI format images are fairly low priority for them.

Re:Fedora 33 by pyrophane on Wednesday October 28, 2020 @10:19AM (#24918979)
Yea, but you can enable the old cgroups pretty easily, and then it only require a couple of firewall instructions to get docker working.

Edit: This still works in 33: https://fedoramagazine.org/docker-and-fedora-32/

The only difference between what they have here and what I do is that I install docker-ce from the 31 repo, as the seem to have some SELinux related change in there that doesn't require me to label volumes like installing moby-engine does.

Re:Fedora 33 by sendhilp on Wednesday October 28, 2020 @10:04AM (#24918831)
Used this workaround successfully for Fedora 32 which turned on cgroupsv2 (haven't tested it on 33, but I imagine it works similarly): https://fedoramagazine.org/docker-and-fedora-32/

One small tweak to the article, for Step 2 I didn't need to use Moby in place of docker as by the time I set things up the `docker-ce` package was available for Fedora 32.

Re:Fedora 33 by bproven on Wednesday October 28, 2020 @10:03AM (#24918824)
Yeah I wish docker would add support. For now I just disable cgroupsv2 via kernel param on my fedora laptop to get docker working.
Re:Fedora 33 by INTPenis on Wednesday October 28, 2020 @09:32AM (#24918526)
I have to add to this that I gave cgroupsv2 an honest chance, still use it on workstations. But on my homelab server I reverted back to cgroupsv1 because 1) Ansible does not yet support podman and 2) podman-compose does not fully support compose. It also confuses compose files with its native pod concept which makes things even more convoluted.
Re:Fedora 33 by yamrzou on Wednesday October 28, 2020 @11:28AM (#24919872)
I switched to Podman, which comes by default with Fedora, no issues so far.
Re:Fedora 33 by jayp1418 on Wednesday October 28, 2020 @09:54AM (#24918729)
How's box working on 33? Any incompatibility?
Re:Fedora 33 by danjac on Wednesday October 28, 2020 @09:26AM (#24918469)
What's the reason for no release/ETA?
Re:Fedora 33 by bluedino on Wednesday October 28, 2020 @10:46AM (#24919307)
Docker was broken on Fedora 32 as well.
Re:Fedora 33 by Szpadel on Wednesday October 28, 2020 @10:28AM (#24919083)
testing docker-ce repository contains release that support cgroupsv2
Re:Fedora 33 by maxk42 on Wednesday October 28, 2020 @11:21AM (#24919761)
Just spent 24 hours grappling with docker issues on fedora 32. In the midst of these issues my OS prompts me to download F33 and I see the migration to btrfs.

I no longer trust the Fedora maintainers.

Re:Fedora 33 by Gracana on Wednesday October 28, 2020 @11:39AM (#24920022)
Sounds like you should be running Red Hat, not Fedora. RHEL has a 10 year support cycle, so you can wait for technologies to mature before you migrate to them.
Re:Fedora 33 by maxk42 on Wednesday October 28, 2020 @02:28PM (#24922355)
btrfs is well over 10 years old and RHEL ditched support for it. My experience with it has not been positive.
Re:Fedora 33 by vondur on Wednesday October 28, 2020 @03:19PM (#24922985)
As Fedora is the testing distro for RedHat Enterprise Linux, I’m guessing they are planning to use BTRFS in upcoming versions.
Re:Fedora 33 by freedomben on Wednesday October 28, 2020 @07:49PM (#24925511)
I wouldn't read that much into it. While a lot of Fedora people also work at Red Hat, Fedora really is a community project. It's quite possible that the community voted to use btrfs as the default file system, even though support is not planned for RHEL.

That said the RHEL people will be paying attention. If btrfs proves successful, I could totally see it going into RHEL 9.

Disclaimer: I work for Red Hat but not on Fedora. I'm just a happy Fedora community member for a little over 10 years now

Re:Fedora 33 by mattdm on Friday October 30, 2020 @04:31PM (#24946595)
Note that your existing system will not be migrated to BTRFS.

I'm sorry to lose your trust. I think that comes from a misunderstanding about expectations. We want to provide a functional, usable system -- but we also are going to change things in new releases, and while we do weigh user impact, we're tilted towards bringing upstream innovation to users. That means we're likely to bring you things like cgroupsv2 sooner rather than later.

If you have these expectations, I hope we're holding to them pretty well. See our mission and foundations page at https://docs.fedoraproject.org/en-US/project/, and hopefully that will make things more clear.