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
-
7
derived packages
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout openSUSE:Factory/docker && cd $_ - Create Badge
Refresh
Refresh
Source Files
Revision 63 (latest revision is 155)
Dominique Leuenberger (dimstar_suse)
accepted
request 540195
from
Aleksa Sarai (cyphar)
(revision 63)
- Add a backport of https://github.com/moby/moby/pull/35424, which fixes a security issue where a maliciously crafted image could be used to crash a Docker daemon. bsc#1066210 CVE-2017-14992 + bsc1066210-0001-vendor-update-to-github.com-vbatts-tar-split-v0.10.2.patch - Add a backport of https://github.com/moby/moby/pull/35399, which fixes a security issue where a Docker container (with a disabled AppArmor profile) could write to /proc/scsi/... and subsequently DoS the host. bsc#1066801 CVE-2017-16539 + bsc1066801-0001-oci-add-proc-scsi-to-masked-paths.patch - Fix bsc#1059011 The systemd service helper script used a timeout of 60 seconds to start the daemon, which is insufficient in cases where the daemon takes longer to start. Instead, set the service type from 'simple' to 'notify' and remove the now superfluous helper script. - fix bsc#1057743: Add a Requires: fix_bsc_1057743 which is provided by the newer version of docker-libnetwork. This is necessary because of a versioning bug we found in bsc#1057743.
Comments 8
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).