-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(deps): update module github.com/docker/docker to v1.13.1 - autoclosed #9
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
renovate
bot
changed the title
chore(deps): update module github.com/docker/docker to v1.13.1
chore(deps): update module github.com/docker/docker to v1.13.1 - autoclosed
Nov 14, 2023
renovate
bot
changed the title
chore(deps): update module github.com/docker/docker to v1.13.1 - autoclosed
chore(deps): update module github.com/docker/docker to v1.13.1
Nov 14, 2023
renovate
bot
force-pushed
the
renovate/github.com-docker-docker-1.x
branch
from
November 14, 2023 18:08
23aa598
to
cffa4a5
Compare
renovate
bot
changed the title
chore(deps): update module github.com/docker/docker to v1.13.1
chore(deps): update module github.com/docker/docker to v1.13.1 - autoclosed
Nov 14, 2023
renovate
bot
changed the title
chore(deps): update module github.com/docker/docker to v1.13.1 - autoclosed
chore(deps): update module github.com/docker/docker to v1.13.1
Nov 15, 2023
renovate
bot
force-pushed
the
renovate/github.com-docker-docker-1.x
branch
from
November 15, 2023 09:01
cffa4a5
to
59c85a3
Compare
renovate
bot
changed the title
chore(deps): update module github.com/docker/docker to v1.13.1
chore(deps): update module github.com/docker/docker to v1.13.1 - autoclosed
Nov 15, 2023
renovate
bot
changed the title
chore(deps): update module github.com/docker/docker to v1.13.1 - autoclosed
chore(deps): update module github.com/docker/docker to v1.13.1
Nov 16, 2023
renovate
bot
force-pushed
the
renovate/github.com-docker-docker-1.x
branch
from
November 16, 2023 04:18
59c85a3
to
09853f0
Compare
renovate
bot
changed the title
chore(deps): update module github.com/docker/docker to v1.13.1
chore(deps): update module github.com/docker/docker to v1.13.1 - autoclosed
Nov 16, 2023
renovate
bot
changed the title
chore(deps): update module github.com/docker/docker to v1.13.1 - autoclosed
chore(deps): update module github.com/docker/docker to v1.13.1
Nov 16, 2023
renovate
bot
force-pushed
the
renovate/github.com-docker-docker-1.x
branch
from
November 16, 2023 21:43
09853f0
to
4db5310
Compare
renovate
bot
changed the title
chore(deps): update module github.com/docker/docker to v1.13.1
chore(deps): update module github.com/docker/docker to v1.13.1 - autoclosed
Nov 17, 2023
renovate
bot
changed the title
chore(deps): update module github.com/docker/docker to v1.13.1 - autoclosed
chore(deps): update module github.com/docker/docker to v1.13.1
Dec 18, 2023
renovate
bot
force-pushed
the
renovate/github.com-docker-docker-1.x
branch
from
December 18, 2023 10:00
4b22d84
to
17e1da1
Compare
renovate
bot
changed the title
chore(deps): update module github.com/docker/docker to v1.13.1
chore(deps): update module github.com/docker/docker to v1.13.1 - autoclosed
Dec 18, 2023
renovate
bot
changed the title
chore(deps): update module github.com/docker/docker to v1.13.1 - autoclosed
chore(deps): update module github.com/docker/docker to v1.13.1
Dec 19, 2023
renovate
bot
force-pushed
the
renovate/github.com-docker-docker-1.x
branch
from
December 19, 2023 12:52
17e1da1
to
158cd03
Compare
renovate
bot
changed the title
chore(deps): update module github.com/docker/docker to v1.13.1
chore(deps): update module github.com/docker/docker to v1.13.1 - autoclosed
Dec 19, 2023
renovate
bot
changed the title
chore(deps): update module github.com/docker/docker to v1.13.1 - autoclosed
chore(deps): update module github.com/docker/docker to v1.13.1
Dec 20, 2023
renovate
bot
force-pushed
the
renovate/github.com-docker-docker-1.x
branch
from
December 20, 2023 01:22
158cd03
to
d68b90a
Compare
renovate
bot
changed the title
chore(deps): update module github.com/docker/docker to v1.13.1
chore(deps): update module github.com/docker/docker to v1.13.1 - autoclosed
Dec 20, 2023
renovate
bot
changed the title
chore(deps): update module github.com/docker/docker to v1.13.1 - autoclosed
chore(deps): update module github.com/docker/docker to v1.13.1
Dec 20, 2023
renovate
bot
force-pushed
the
renovate/github.com-docker-docker-1.x
branch
from
December 20, 2023 07:24
d68b90a
to
58961fe
Compare
renovate
bot
changed the title
chore(deps): update module github.com/docker/docker to v1.13.1
chore(deps): update module github.com/docker/docker to v1.13.1 - autoclosed
Dec 20, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v1.4.2-0.20190219180918-740349757396
->v1.13.1
Release Notes
docker/docker (github.com/docker/docker)
v1.13.1
Compare Source
1.13.1 (2017-02-08)
IMPORTANT: On Linux distributions where
devicemapper
was the default storage driver,the
overlay2
, oroverlay
is now used by default (if the kernel supports it).To use devicemapper, you can manually configure the storage driver to use through
the
--storage-driver
daemon option, or by setting "storage-driver" in thedaemon.json
configuration file.
IMPORTANT: In Docker 1.13, the managed plugin api changed, as compared to the experimental
version introduced in Docker 1.12. You must uninstall plugins which you installed with Docker 1.12
before upgrading to Docker 1.13. You can uninstall plugins using the
docker plugin rm
command.If you have already upgraded to Docker 1.13 without uninstalling
previously-installed plugins, you may see this message when the Docker daemon
starts:
To manually remove all plugins and resolve this problem, take the following steps:
/var/lib/docker/plugins/
.Contrib
Remote API (v1.26) & Client
Runtime
docker system df
#30378docker inspect
when Swarm certificates were expired. #29246Plugins
docker plugin upgrade
#29414Windows
Downloads
v1.13.0
Compare Source
1.13.0 (2017-01-18)
IMPORTANT: In Docker 1.13, the managed plugin api changed, as compared to the experimental
version introduced in Docker 1.12. You must uninstall plugins which you installed with Docker 1.12
before upgrading to Docker 1.13. You can uninstall plugins using the
docker plugin rm
command.If you have already upgraded to Docker 1.13 without uninstalling
previously-installed plugins, you may see this message when the Docker daemon
starts:
To manually remove all plugins and resolve this problem, take the following steps:
/var/lib/docker/plugins/
.Builder
docker build
#24978--network
todocker build
#27702--label
flag ondocker build
anddocker run
#26027USER
in builder on Windows #28415Contrib
make deb
support for aarch64 #27625Distribution
~/.docker/trust/private
directory, not just under~/.docker/trust/private/root_keys
or~/.docker/trust/private/tuf_keys
docker/notary#981Logging
docker logs --tail
returned less lines than expected #28203Networking
--attachable
network support to enabledocker run
to work in swarm-mode overlay network #25962--publish
option indocker service create
#27917 and #28943FORWARD
policy toDROP
#28257--publish
flag ondocker run
not working with IPv6 addresses #27860--fixed-cidr
to not have the correct addresses #26659docker network inspect
#26130docker network inspect
for swarm overlay networks #28078Plugins
--force
ondocker plugin remove
#25096docker plugin ls
#25556-f
/--format
todocker plugin inspect
#25990docker plugin create
command #28164docker plugin install
into two API call/privileges
and/pull
#28963Remote API (v1.25) & Client
docker stack deploy
from a Compose file #27998--format
flag todocker info
#23808--name
fromdocker volume create
#23830docker stack ls
#23886is-task
ps filter #24411--env-file
flag todocker service create
#24844--format
ondocker stats
#24987docker node ps
default toself
in swarm node #25214--group
indocker service create
#25317--no-trunc
to service/node/stack ps output #25337ContainerAttachOptions
so go clients can request to retrieve container logs as part of the attach process #26718Isolation
to the /info endpoint #26255userns
to the /info endpoint #27840--format
flag tonetwork ls
andvolume ls
#23475docker inspect
command to inspect any kind of resource #23614--entrypoint
indocker run
ordocker create
#23718docker image
anddocker container
commands for more consistency #26025COMMAND
column fromservice ls
output #28029--format
todocker events
#26268docker node ps
#26299docker images
output #26303--dns-option
todocker run
#28186Manager Addresses
in the output ofdocker info
#28042docker images
#27872Runtime
--experimental
daemon flag to enable experimental features, instead of shipping them in a separate build #27223--shutdown-timeout
daemon flag to specify the default timeout (in seconds) to stop containers gracefully before daemon exit #23036--stop-timeout
to specify the timeout value (in seconds) for individual containers to stop #22566--userland-proxy-path
to allow configuring the userland proxy instead of using the hardcodeddocker-proxy
from$PATH
#26882--init
ondockerd
and ondocker run
to use tini a zombie-reaping init process as PID 1 #26061 #28037--init-path
to allow configuring the path to thedocker-init
binary #26941docker run --rm
by moving it from the client to the daemon #20848--cpu-rt-period
and--cpu-rt-runtime
flags, allowing containers to run real-time threads whenCONFIG_RT_GROUP_SCHED
is enabled in the kernel #23430service tasks --filter
#24850docker stats
support in Windows #25737--pid=host
and--net=host
when--userns=host
#25771container
,image
, anddaemon
operations #25820docker stats
withNetworkDisabled=true
#25905docker top
support in Windows #25891getent
#27599docker system
command withdf
andprune
subcommands for system resource management, as well asdocker {container,image,volume,network} prune
subcommands #26108 #27525 / #27525docker cp
failing to copy to a container's volume dir on CentOS with devicemapper #28047--seccomp-profile
daemon flag to specify a path to a seccomp profile that overrides the default #26276docker inspect
when--default-ulimit
is set on daemon #26405TERM
environment variable ondocker exec -t
#26461--stop-signal
setting upondocker kill
#26464Swarm Mode
docker service inspect --pretty
#26906docker service ps
output more bearable by shortening service IDs in task names #28088docker node ps
default to the current node #25214--dns
, --dns-opt
, and--dns-search
to service create. #27567--force
todocker service update
#27596-q
todocker service ps
#27654docker service ls
#27710--name
flag fromdocker service update
. This flag is only functional ondocker service create
, so was removed from theupdate
command #26988--hostname
todocker service create
#27857--host
todocker service create
, and--host-add
,--host-rm
todocker service update
#28031--tty
flag todocker service create
/update
#28076--update-max-failure-ratio
,--update-monitor
and--rollback
flags todocker service update
#26421docker swarm init
running inside a container #26457docker service logs
command to view logs for a service #28089docker service create
andupdate
#28173-f
) flag fordocker node rm --force
anddocker swarm leave --force
#28196--max-snapshots
,--snapshot-interval
) #27997Volume
--force
flag indocker volume rm
to forcefully purge the data of the volume that has already been deleted #23436docker volume inspect
to show all options used when creating the volume #26671Security
/sys/firmware/**
from being accessed with apparmor #26618DEPRECATION
docker daemon
command as deprecated. The daemon is moved to a separate binary (dockerd
), and should be used instead #26834repo:shortid
syntax ondocker pull
#27207d_type
for overlay and overlay2 storage drivers #27433MAINTAINER
in Dockerfile #25466filter
param for endpoint/images/json
#27872NetworkSettings
#28437Downloads
v1.12.6
Compare Source
1.12.6 (2017-01-10)
IMPORTANT: Docker 1.12 ships with an updated systemd unit file for rpm
based installs (which includes RHEL, Fedora, CentOS, and Oracle Linux 7). When
upgrading from an older version of docker, the upgrade process may not
automatically install the updated version of the unit file, or fail to start
the docker service if;
/usr/lib/systemd/system/docker.service
) contains local changes, or-H fd://
in theExecStart
directiveStarting the docker service will produce an error:
or
To resolve this:
version that ships with docker 1.12
Requires=docker.socket
directive from the/usr/lib/systemd/system/docker.service
file if present-H fd://
from theExecStart
directive (both in the main unit file, and in any drop-in files present).After making those changes, run
sudo systemctl daemon-reload
, andsudo systemctl restart docker
to reload changes and (re)start the docker daemon.NOTE: Docker 1.12.6 will correctly validate that either an IPv6 subnet is provided or
that the IPAM driver can provide one when you specify the
--ipv6
option.If you are currently using the
--ipv6
option without specifying the--fixed-cidr-v6
option, the Docker daemon will refuse to start with thefollowing message:
To resolve this error, either remove the
--ipv6
flag (to preserve the samebehavior as in Docker 1.12.3 and earlier), or provide an IPv6 subnet as the
value of the
--fixed-cidr-v6
flag.In a similar way, if you specify the
--ipv6
flag when creating a networkwith the default IPAM driver, without providing an IPv6
--subnet
, networkcreation will fail with the following message:
To resolve this, either remove the
--ipv6
flag (to preserve the same behavioras in Docker 1.12.3 and earlier), or provide an IPv6 subnet as the value of the
--subnet
flag.The network network creation will instead succeed if you use an external IPAM driver
which supports automatic allocation of IPv6 subnets.
Runtime
Downloads
Regular
With experimental features
v1.12.5
Compare Source
1.12.5 (2016-12-15)
IMPORTANT: Docker 1.12 ships with an updated systemd unit file for rpm
based installs (which includes RHEL, Fedora, CentOS, and Oracle Linux 7). When
upgrading from an older version of docker, the upgrade process may not
automatically install the updated version of the unit file, or fail to start
the docker service if;
/usr/lib/systemd/system/docker.service
) contains local changes, or-H fd://
in theExecStart
directiveStarting the docker service will produce an error:
or
To resolve this:
version that ships with docker 1.12
Requires=docker.socket
directive from the/usr/lib/systemd/system/docker.service
file if present-H fd://
from theExecStart
directive (both in the main unit file, and in any drop-in files present).After making those changes, run
sudo systemctl daemon-reload
, andsudo systemctl restart docker
to reload changes and (re)start the docker daemon.NOTE: Docker 1.12.5 will correctly validate that either an IPv6 subnet is provided or
that the IPAM driver can provide one when you specify the
--ipv6
option.If you are currently using the
--ipv6
option without specifying the--fixed-cidr-v6
option, the Docker daemon will refuse to start with thefollowing message:
To resolve this error, either remove the
--ipv6
flag (to preserve the samebehavior as in Docker 1.12.3 and earlier), or provide an IPv6 subnet as the
value of the
--fixed-cidr-v6
flag.In a similar way, if you specify the
--ipv6
flag when creating a networkwith the default IPAM driver, without providing an IPv6
--subnet
, networkcreation will fail with the following message:
To resolve this, either remove the
--ipv6
flag (to preserve the same behavioras in Docker 1.12.3 and earlier), or provide an IPv6 subnet as the value of the
--subnet
flag.The network network creation will instead succeed if you use an external IPAM driver
which supports automatic allocation of IPv6 subnets.
Runtime
Networking
--ipv6
and no ipv6--subnet
in older docker versions #29416Contrib
Downloads
Regular
With experimental features
v1.12.4
Compare Source
1.12.4 (2016-12-12)
IMPORTANT: Docker 1.12 ships with an updated systemd unit file for rpm
based installs (which includes RHEL, Fedora, CentOS, and Oracle Linux 7). When
upgrading from an older version of docker, the upgrade process may not
automatically install the updated version of the unit file, or fail to start
the docker service if;
/usr/lib/systemd/system/docker.service
) contains local changes, or-H fd://
in theExecStart
directiveStarting the docker service will produce an error:
or
To resolve this:
version that ships with docker 1.12
Requires=docker.socket
directive from the/usr/lib/systemd/system/docker.service
file if present-H fd://
from theExecStart
directive (both in the main unit file, and in any drop-in files present).After making those changes, run
sudo systemctl daemon-reload
, andsudo systemctl restart docker
to reload changes and (re)start the docker daemon.NOTE: Docker 1.12.4 will correctly validate that either an IPv6 subnet is provided or
that the IPAM driver can provide one when you specify the
--ipv6
option.If you are currently using the
--ipv6
option without specifying the--fixed-cidr-v6
option, the Docker daemon will refuse to start with thefollowing message:
To resolve this error, either remove the
--ipv6
flag (to preserve the samebehavior as in Docker 1.12.3 and earlier), or provide an IPv6 subnet as the
value of the
--fixed-cidr-v6
flag.In a similar way, if you specify the
--ipv6
flag when creating a networkwith the default IPAM driver, without providing an IPv6
--subnet
, networkcreation will fail with the following message:
To resolve this, either remove the
--ipv6
flag (to preserve the same behavioras in Docker 1.12.3 and earlier), or provide an IPv6 subnet as the value of the
--subnet
flag.The network network creation will instead succeed if you use an external IPAM driver
which supports automatic allocation of IPv6 subnets.
Runtime
docker pull
#29297Swarm Mode
Networking
Logging
Contrib
Downloads
Regular
With experimental features
v1.12.3
Compare Source
1.12.3 (2016-10-26)
IMPORTANT: Docker 1.12 ships with an updated systemd unit file for rpm
based installs (which includes RHEL, Fedora, CentOS, and Oracle Linux 7). When
upgrading from an older version of docker, the upgrade process may not
automatically install the updated version of the unit file, or fail to start
the docker service if;
/usr/lib/systemd/system/docker.service
) contains local changes, or-H fd://
in theExecStart
directiveStarting the docker service will produce an error:
or
To resolve this:
version that ships with docker 1.12
Requires=docker.socket
directive from the/usr/lib/systemd/system/docker.service
file if present-H fd://
from theExecStart
directive (both in the main unit file, and in any drop-in files present).After making those changes, run
sudo systemctl daemon-reload
, andsudo systemctl restart docker
to reload changes and (re)start the docker daemon.Runtime
Swarm Mode
Networking
Logging
Contrib
Downloads
Regular
With experimental features
v1.12.2
Compare Source
1.12.2 (2016-10-06)
IMPORTANT: Docker 1.12 ships with an updated systemd unit file for rpm
based installs (which includes RHEL, Fedora, CentOS, and Oracle Linux 7). When
upgrading from an older version of docker, the upgrade process may not
automatically install the updated version of the unit file, or fail to start
the docker service if;
/usr/lib/systemd/system/docker.service
) contains local changes, or-H fd://
in theExecStart
directiveStarting the docker service will produce an error:
or
To resolve this:
version that ships with docker 1.12
Requires=docker.socket
directive from the/usr/lib/systemd/system/docker.service
file if present-H fd://
from theExecStart
directive (both in the main unit file, and in any drop-in files present).After making those changes, run
sudo systemctl daemon-reload
, andsudo systemctl restart docker
to reload changes and (re)start the docker daemon.Runtime
docker ps
#26049dm.use_deferred_removal
is enabled #24740Networking
ingress_sbox
docker/libnetwork#1449Swarm Mode
service create
orservice update
docker/swarmkit#1495Contrib
dockerd
instead ofdocker daemon
#25869Windows
Downloads
Regular
With experimental features
v1.12.1
Compare Source
1.12.1 (2016-08-18)
IMPORTANT: Docker 1.12 ships with an updated systemd unit file for rpm
based installs (which includes RHEL, Fedora, CentOS, and Oracle Linux 7). When
upgrading from an older version of docker, the upgrade process may not
automatically install the updated version of the unit file, or fail to start
the docker service if;
/usr/lib/systemd/system/docker.service
) contains local changes, orConfiguration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.