Docker is considering a flatpak. Upvote here: https://github.com/docker/roadmap/issues/593
flatpak is like a cross-distro snap that actually works. some of the apps are buggy at the fringes, but i've been opening issues to smooth them out. some of the apps like VS Code claim to be from microsoft, but are... unofficial?
In Flathub: One million active users and growingdocker
roadmap
Systems & Infrastructure2020–2024
docker / roadmap
roadmap
Welcome to the Public Roadmap for All Things Docker! We welcome your ideas.
41Distinct people
47Mentions
0Explicit recommenders
1.9KGitHub stars
What to know before exploring
What it is
Welcome to the Public Roadmap for All Things Docker! We welcome your ideas.
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 12:24:10 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year47 dated mentions
Observed mentions: 2020-04-13 20:02:51 UTC to 2024-01-29 17:35:40 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 11 | 4 | 7 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 16 | 3 | 13 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 11 | 1 | 10 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 5 | 0 | 5 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 4 | 1 | 3 |
From the project README
An excerpt from the repository, fetched Nov 13, 2026.
Read the project’s introduction
Docker Roadmap
Thank you for the interest in Docker and our products!
This is the public roadmap for Docker Products and Services (Hub, Desktop, Engine, docker-compose, Build Cloud).
Introduction
We want to share with our customers what we plan to do early and often so we can get your feedback on if these are the right things for us to be focusing on. This also allows our customers to make early decisions based on what we are/are not building.
See the roadmap »
Contribute to our roadmap »
Early Access to features
For users of Docker Desktop interested in early access to new features please join our Developer Preview Program.
Participate in User Research
During these live feedback sessions we will often show work in progress features or ideas to get your input on, or ask you more about how you use Docker to discover any pain points when working with the product. We use these insights to help prioritize our roadmap and improve the user experience. Each session is typically 30 minutes to an hour. If you would like to take part in one of our user research studies please sign up and we will reach out to you when we have something to research or test.
Security
Please do not create a public github issue. If you discover a potential security issue in this project we ask that you notify Docker Security send your report privately to security@docker.com. Please do not create a public github issue.
FAQs
Q: Is everything on the roadmap?
A: Almost everything related to features, we might keep the odd feature a surprise if we really aren’t sure about it. We also won’t be tracking all of our bugs here, we have separate repos for these:
Docker Hub
Docker Engine
Docker Desktop Linux
Docker Desktop Windows
Docker Desktop Mac
Docker Build Cloud
Q: What do the roadmap categories mean?
Shipped - Hopefully you are enjoying it! Give us feedback on how it is working!
Almost There - We are applying the finishing touches. Things in this bucket you can expect to be shipped within 2-4 weeks.
We're Writing the Code - Actively in development, we are trying to get this out to you in a good state as soon as we can.
Investigating - We're thinking about it. This might mean we're still designing, or thinking through how this might work. This is a great phase to send how you want to see something implemented! We'd love to see your usecase or design ideas here.
Q: Why are there no dates on your roadmap?
A: Because we know things change and we want the room to do the right thing by fixing security issues as they come up or helping people out where they need. This means we might have to change our priorities and don’t want to let people down.
Q: How can I provide feedback or ask for more information?
A: Please open an issue in this repo! If the issue is a bug or security issue, please follow the separate instructions above.
Q: How can I request a feature be added to the roadmap?
A: Please open an issue! You can read about how to contribute here. Community submitted issues will be tagged "Proposed" and will be reviewed by the team.
Q: Will you accept a pull request?
A: We haven't worked out how pull requests should work for a public roadmap page, but we will take all PRs very seriously and review for inclusion. Read about contributing. We review these each week.
License
This library is licensed under the Creative Commons Attribution-ShareAlike 4.0 International License.
If you are curious about anything else Docker related then please head over to: www.docker.com
Read the full README on GitHubWhat Hacker News says
47 sourcesThe Docker team is now considering a flatpak. Please upvote. https://github.com/docker/roadmap/issues/593#issuecomment-18...
In I took Linux Mint for a spinThe Docker team is now considering a flatpak: https://github.com/docker/roadmap/issues/593#issuecomment-18...
In I took Linux Mint for a spinDocker considering flatpak and snap apps for Linux (please upvote)
1 points · Open discussionx86-64 docker containers?
https://github.com/docker/roadmap/issues/384 is still open. :(
In Apple unveils M3, M3 Pro, and M3 MaxIn case you need to run x86 containers: Docker now has Rosetta support - but it's buggy.
https://github.com/docker/roadmap/issues/384
Without Rosetta it uses relatively slow Qemu emulation.
In Ask HN: Is MacBook Pro 14 M1 16/512 still a great choice for development?It seems a bit confusing. Here's some context:
https://github.com/docker/roadmap/issues/175
In De-cloud and de-k8s – bringing our apps back homeFrom the article:
> If you are able to completely delete your organisation, then you could re-create it as a free personal account. That should be enough to reserve the name to prevent hostile take-over. Has Docker forgotten Remember leftpad?
>
> This is unlikely that large projects can simply delete their organisation and all its images.
>
> If that's the case, and you can tolerate some downtime, you could try the following:
> - Create a new personal user account
> - Mirror all images and tags required to the new user account
> - Delete the organisation
> - Rename the personal user account to the name of the organisation
Seems like no?
We cannot rename personal accounts on Docker Hub in 2023. There is no such feature in account settings, and here is the related issue:
https://github.com/docker/roadmap/issues/44
So, at the moment, any pub
Read the rest
lic organization images are doomed to be lost, if they won't pay.
We've started using Rush [1] at Buffer. Teams have been slowly migrating, and it has been great so far. We had (too many) repos with their own workflow and way too many different ways to build services, which has been annoying to maintain. I know teams use Rush at scale: Tiktok has ~450 projects, and Microsoft said they have ~700 projects.
To deploy the services locally, we use Tilt[2] (K8s for local). We want to be able to reproduce production as much as possible and remove developer overhead on how things work locally and in production.
Then come the issues with Docker and large node code bases:
1 challenge with large monorepos is the huge node_modules folder (rush among other tools put packages into a single large node_modules folder, and symlink every dependency there. It can contain millions of files and GBs, depending on how many 3r
Read the rest
d-party libraries you use). On Linux, you can mount it without issues, but Mac has performance issues[3] with large folders.
We pre-build that huge node_modules into a "base" image, and each service in the monorepo pulls that base image and only mounts what's necessary (a few mb). So we can save that npm build time and don't need to copy all those files inside the containers. It is fine because package.json does not change that often. You need to do this pre-build locally then in your CI/CD -> dockerhub, so everyone can get it.
Another challenge is that you need to "watch" files to rebuild them. Watching all your files inside the monorepo isn't really viable. We use a dependency graph to know what services to watch and then copy the built files inside the Tilt containers.
Hope this can help people.
[1] https://rushjs.io
[2] https://tilt.dev/
[3] https://github.com/docker/roadmap/issues/7
It seems this may get better soon, when they run via Rosetta 2 rather than QEMU(?)
https://github.com/docker/roadmap/issues/384
In Podman Desktop: A Free OSS Alternative to Docker DesktopIt's a Docker for Mac issue: https://github.com/docker/roadmap/issues/7
In It's not Ruby that's slow, it's your database> Running the exact same docker image [...]
I don't think Docker supports using Rosetta to run x86 binaries inside arm64 containers. Here's an open feature request for it: https://github.com/docker/roadmap/issues/384
In Running Intel Binaries in Linux VMs with RosettaThis should be great when it gets integrated with Docker. And apparently that's high priority: https://github.com/docker/roadmap/issues/384
In Running Intel Binaries in Linux VMs with RosettaOne big feature for me is much improved Virtualization framework. I'm eager for https://github.com/docker/roadmap/issues/384 to be closed. Must solve some QoL issues for me.
In macOS Ventura is now availableIt still exists but there is zero development on it. They left it in a kind of half finished state imho with some pretty annoying gaps in the workflow around updating configs/secrets, one time tasks, etc. There's zero future or updates in its roadmap: https://github.com/docker/roadmap/issues/175
In Docker October 2022 Pricing Change FAQShowing the 15 most recent of 47 sources. Enable JavaScript to search and browse every indexed mention.