docker
http://www.docker.io
Docker complements LXC with a high-level API which operates at the process level. It runs unix processes with strong guarantees of isolation and repeatability across servers.
Docker is a great building block for automating distributed systems: large-scale web deployments, database clusters, continuous deployment systems, private PaaS, service-oriented architectures, etc.
- Developed at Virtualization:containers
-
6
derived packages
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout openSUSE:Factory/docker && cd $_ - Create Badge
Refresh
Refresh
Source Files
| Filename | Size | Changed |
|---|---|---|
|
0001-SECRETS-daemon-allow-directory-creation-in-ru |
0000002662 2.6 KB | |
|
0002-SECRETS-SUSE-implement-SUSE-container-secrets |
0000016902 16.5 KB | |
|
0003-BUILD-SLE12-revert-graphdriver-btrfs-use-kern |
0000001643 1.6 KB | |
|
0004-bsc1073877-apparmor-clobber-docker-default-pr |
0000003316 3.24 KB | |
|
0005-SLE12-revert-apparmor-remove-version-conditio |
0000009849 9.62 KB | |
| 80-docker.rules | 0000000345 345 Bytes | |
| README_SUSE.md | 0000008196 8 KB | |
| _service | 0000001156 1.13 KB | |
| docker-28.1.1_ce_01f442b84.tar.xz | 0010524888 10 MB | |
| docker-audit.rules | 0000001269 1.24 KB | |
| docker-buildx-0.23.0.tar.xz | 0008093360 7.72 MB | |
| docker-cli-28.1.1_ce.tar.xz | 0004234444 4.04 MB | |
| docker-daemon.json | 0000000119 119 Bytes | |
| docker-integration.sh | 0000008849 8.64 KB | |
| docker-rpmlintrc | 0000000522 522 Bytes | |
| docker.changes | 0000212952 208 KB | |
| docker.service | 0000001677 1.64 KB | |
| docker.socket | 0000000541 541 Bytes | |
| docker.spec | 0000019990 19.5 KB | |
| docker.sysusers | 0000000208 208 Bytes | |
| sysconfig.docker | 0000000190 190 Bytes |
Comments 9
I'm trying to update this to 1.13.0, and just having an odd time of it. Where do we get the tar.xz files from? I can't find them anywhere by the checksum online.
Anyone coming close to building a package for 1.13.0 per chance? I'm busting for an update as the present 1.12.6 is having some bizarre bugs that I'm hoping are fixed in 1.13.0. For details on these bugs please see this thread https://forums.opensuse.org/showthread.php/522711-Why-can-t-I-seem-to-launch-RuneScape-s-NXT-Client-using-Docker-on-openSUSE on the openSUSE forums.
Why has this not be updated to the stable release of ce: 17.09.0-ce
It's fairly complicated to package docker actually. I took a stab at it and its quite a mess (https://build.opensuse.org/package/show/home:avindra/docker?expand=0). Not only is it made of many different components, but it is also written in Go which has no real standards around dependency management.
Docker itself has one of the most complex builds of any project I've seen.
Awesome! I'm glad to hear that you are working on it. I believe you on the difficulty, docker has become a complex beast while it has matured.
Is there a reason why the completion file for zsh is
dockerinstead of_docker? I have to create a symlink_dockerpointing todockerin/etc/zsh_completion.dto make it work with zsh.Hi Aleksa,
thanks for maintaining the docker package!
The latest update to docker docker 26.1.5_ce-9.1 broke container networking for me. Rolling back to a previous snapper snapshot with docker 26.1.5_ce-8.1 makes container networking work again.
See here for more details: https://forums.opensuse.org/t/update-on-19-november-2024-broke-docker-container-networking-docker-26-1-5-ce-9-1/180499
What could be the reason?
Please make a Bugzilla report, comments on openSUSE:Factory are not the right place for bug reports (and neither is the forum to be honest). If you use
DOCKER_NETWORK_OPTSplease mention that in the bug report (the forum is down for me so I can't read the thread).Hey Aleksa, I appreciate the work you do here, as I could probably never do it myself. Without being pushy, I just wanted to ask if you have any plans to update to Docker 28 in the near future. In releases prior to 28.0.0, Docker always set the default policy of the IPv6 FORWARD chain to DROP. In releases 28.0.0 and newer, it will only set this policy if it enables IPv6 forwarding itself. This has always been the behavior for IPv4 forwarding. This breaks ipv6 support for other services like podman that are installed at the same time, so docker 28 is a really important release in terms of ipv6 support.
Thanks and regards ;)