Package Details: docker-bin 20.10.7-1

Git Clone URL: https://aur.archlinux.org/docker-bin.git (read-only, click to copy)
Package Base: docker-bin
Description: Pack, ship and run any application as a lightweight container, using official binaries
Upstream URL: https://www.docker.com/
Licenses: Apache
Conflicts: docker, docker-ce, docker-git
Provides: docker, docker-ce
Submitter: javmorin
Maintainer: javmorin
Last Packager: javmorin
Votes: 11
Popularity: 0.48
First Submitted: 2016-08-18 18:48
Last Updated: 2021-06-03 01:13

Required by (154)

Sources (8)

Pinned Comments

javmorin commented on 2018-11-17 19:46

IMPORTANT: Please switch to the docker-bin package.

This is very likely the final "real" release of the docker-stable-bin package. At this point, docker has eliminated the edge/stable distinction and so the docker-bin should now be considered stable. At the next docker release, I will likely turn this package into a meta-package depending on docker-bin.

As for this "final" release, there are some changes: Docker is now shipped with conflicting (non-namespaced) versions of runc and containerd, the back end components for running containers. The community package for docker has switched to using the discreet packages for those components, so I have done the same for docker-stable-bin.

javmorin commented on 2018-11-17 19:45

Docker is now shipped with conflicting (non-namespaced) versions of runc and containerd, the back end components for running containers. The community package for docker has switched to using the discreet packages for those components, so I have done the same for docker-bin. I may re-assess this if the community packages get out-of-sync from what docker is packaging, but as they are not actually part of docker itself, I don't want to do that unless there is need of it.

javmorin commented on 2017-12-28 19:02

IMPORTANT: You must stop all containers and plugins BEFORE upgrading to Docker CE 17.12.

Docker CE 17.12 and later won't recognize containers started with previous Docker versions. If using Live Restore, you must stop all containers before upgrading to Docker CE 17.12. If you don't, any containers started by Docker versions that predate 17.12 won't be recognized by Docker after the upgrade and will keep running, un-managed, on the system.

See https://github.com/moby/moby/pull/35812 for details

javmorin commented on 2017-12-28 19:01

IMPORTANT: You must stop all containers and plugins BEFORE upgrading to Docker CE 17.12.

Docker CE 17.12 and later won't recognize containers started with previous Docker versions. If using Live Restore, you must stop all containers before upgrading to Docker CE 17.12. If you don't, any containers started by Docker versions that predate 17.12 won't be recognized by Docker after the upgrade and will keep running, un-managed, on the system.

See https://github.com/moby/moby/pull/35812 for details

Latest Comments

1 2 Next › Last »

bpier commented on 2021-01-30 18:11

@javmorin Thank you :)

I tried to update without clearing the cache (using yay), just to confirm it was coming from the deb file: it worked perfectly! And thanks for the explanation, I will remember clearing the cache next time.

javmorin commented on 2021-01-30 18:06

@bpier it's likely because you have the previous version of a source file cached. I do recommend clearing your source file cache before building this package, as there are some source files that are downloaded which do not have versioned names. I have just changed the package to use the versioned name for the deb file (the likely culprit for you) but there are other files that this applies to as well.

bpier commented on 2021-01-30 15:50

I am getting an error since (I think) the last update:

==> ERROR: One or more files did not pass the validity check!
error downloading sources: docker-bin

javmorin commented on 2018-11-17 19:46

IMPORTANT: Please switch to the docker-bin package.

This is very likely the final "real" release of the docker-stable-bin package. At this point, docker has eliminated the edge/stable distinction and so the docker-bin should now be considered stable. At the next docker release, I will likely turn this package into a meta-package depending on docker-bin.

As for this "final" release, there are some changes: Docker is now shipped with conflicting (non-namespaced) versions of runc and containerd, the back end components for running containers. The community package for docker has switched to using the discreet packages for those components, so I have done the same for docker-stable-bin.

javmorin commented on 2018-11-17 19:45

Docker is now shipped with conflicting (non-namespaced) versions of runc and containerd, the back end components for running containers. The community package for docker has switched to using the discreet packages for those components, so I have done the same for docker-bin. I may re-assess this if the community packages get out-of-sync from what docker is packaging, but as they are not actually part of docker itself, I don't want to do that unless there is need of it.

javmorin commented on 2018-03-19 16:03

@xoac as indicated in the package description, this package includes the official built/tested binaries from docker and is not recompiled with whatever version of golang is currently installed. Otherwise this package is the same as community/docker

xoac commented on 2018-03-19 11:41

What is difference between this pkg and https://www.archlinux.org/packages/community/x86_64/docker/ ?!

javmorin commented on 2018-03-05 19:04

@kevlar1818 I don't see why not. I will have to do a bit of research on that from both the packaging side (including verifying component availability in Arch Linux ARM) as well as any architecture translations (since the only arch specifically matching is aarch64). If you have any knowledge on that last bit, please pass it along.

kevlar1818 commented on 2018-03-05 18:31

Could this be generalized to accept any architecture provided here?

https://download.docker.com/linux/static/

I'd like to use this package on Arch Linux ARM.

javmorin commented on 2017-12-28 19:02

IMPORTANT: You must stop all containers and plugins BEFORE upgrading to Docker CE 17.12.

Docker CE 17.12 and later won't recognize containers started with previous Docker versions. If using Live Restore, you must stop all containers before upgrading to Docker CE 17.12. If you don't, any containers started by Docker versions that predate 17.12 won't be recognized by Docker after the upgrade and will keep running, un-managed, on the system.

See https://github.com/moby/moby/pull/35812 for details