Skip to content

Latest commit

 

History

History
552 lines (377 loc) · 33.1 KB

CHANGELOG.md

File metadata and controls

552 lines (377 loc) · 33.1 KB
Raw

Changelog

Due to the nature of versioning and the fact this repository houses multiple Docker images, the change log is more of a chronological record of events. Including improvements that are made over time without a specific release, and the actual releases.

Each release records it's own specific changes in a VERSIONS.md file.

2019.04.13

  • alpine-nodejs: upgraded Node.js to v8.13.0.
  • alpine-nodejs: upgraded Node.js to v8.14.0.
  • alpine-nodejs: upgraded Node.js to v8.15.0.

Releases

2019.04.11

  • alpine-nodejs: upgraded Node.js to v8.12.0.

Releases

2019.04.10

  • alpine-nodejs: upgraded Node.js to v8.9.0.
  • alpine-nodejs: upgraded Node.js to v8.10.0.
  • alpine-nodejs: upgraded Node.js to v8.11.0.

Releases

2019.04.09

  • alpine-nodejs: upgraded Node.js to v8.4.0.
  • alpine-nodejs: upgraded Node.js to v8.5.0.
  • alpine-nodejs: upgraded Node.js to v8.6.0.
  • alpine-nodejs: upgraded Node.js to v8.7.0.
  • alpine-nodejs: upgraded Node.js to v8.8.0.

Releases

2019.04.08

  • alpine-nodejs: upgraded Node.js to v8.3.0.

Releases

2019.04.04

  • alpine-nodejs: upgraded Node.js to v8.0.0.
  • alpine-nodejs: upgraded alpine-base to 3.3.0.
  • alpine-nodejs: upgraded Node.js to v8.1.0.
  • alpine-nodejs: upgraded Node.js to v8.2.0.

Releases

2019.03.31

  • alpine-base: upgraded Alpine to v3.9.
  • alpine-base: upgraded s6-overlay to v1.22.1.0.

Releases

2017.10.31

  • alpine-nodejs: upgraded to Node.js v6.11.4.

Releases

2017.10.29

  • alpine-nodejs: upgraded to Node.js v6.11.2.
  • alpine-nodejs: upgraded to Node.js v6.11.2.

Releases

2017.10.28

  • alpine-nodejs: upgraded to Node.js v6.11.1.

Releases

2017.10.27

  • alpine-nodejs: upgraded to Node.js v6.10.3.
  • alpine-nodejs: upgraded to Node.js v6.11.0.

Releases

2017.10.26

  • alpine-nodejs: upgraded to Node.js v6.10.1.
  • alpine-nodejs: upgraded to Node.js v6.10.2.

Releases

2017.07.05

  • alpine-consul: updated consul to v0.8.5. Transitioned from beta to full release.
  • alpine-consul-base: updated consul-template to v0.19.0. Transitioned from beta to full release.
  • alpine-consul-ui: transitioned from beta to full release.
  • alpine-consul-redis: updated Redis to v3.2.5.
  • alpine-consul-nginx: transitioned from beta to full release.
  • alpine-consul-nodejs: transitioned from beta to full release.

Releases

2017.06.14

  • alpine-consul:
    • added util-linux package for uuidgen binary.
    • consul-node-id now uses uuidgen for better UUID generation that doesn't clash.
    • Upgraded Consul to v0.8.4.

Releases

2017.06.08

  • alpine-consul-base: updated consul-template configuration file to use a stanza rather than a string.

Releases

2017.06.02

  • alpine-consul, alpine-consul-base, alpine-consul-ui:
    • upgraded to Consul v0.8.3.
    • added the new -data-id argument (customisable via replacing the /usr/bin/consul-node-id script).
    • added the -data-dir argument (customisable via the CONSUL_DATA_DIR ENV variable).
    • exposed 8600 and 8600/udp.
  • alpine-consul-base: upgraded consul-template to v0.18.5.
  • alpine-consul-base: added the CONSUL_TEMPLATE_RUNAS ENV variable to customise which user runs consul-template.
  • alpine-consul-base: added the CONSUL_RUNAS ENV variable to customise which user runs consul.
  • alpine-consul-redis: upgrade Redis to v3.2.5-r0.
  • alpine-consul: added the GO_DNSMASQ_RUNAS ENV variable to customise which user runs go-dnsmasq.
  • alpine-consul: added the CONSUL_BOOTSTRAP_DEBUG to show debug messages. Set to true. Information will be output by the consul-available, consul-join and consul-join-wan scripts.
  • alpine-consul: added the CONSUL_AVAILABLE_SLEEP ENV variable to customise the amount of seconds to sleep between checking for other consul servers.

2017.05.31

Releases

2017.05.09

  • alpine-nginx-nodejs: upgraded to Node.js v6.4.0.

Releases

2017.05.08

  • alpine-nginx-nodejs: upgraded to Node.js v6.3.1.
  • alpine-base: created new beta branch abh-master from PR #72:
    • Upgraded to Alpine v3.5.
    • Add the libcap package.
    • Update s6-overlay to v1.19.1.1.
  • alpine-base: move away from ADD to COPY, inline with Docker best practices.
  • alpine-base: renamed GODNSMASQ_VERSION to GO_DNSMASQ_VERSION.
  • alpine-base: added GO_DNSMASQ_RUNAS for easy configuration of the user in which go-dnsmasq will run as. This is to support environments in which setcap doesn't work.

Releases

2017.05.07

  • alpine-nginx-nodejs: upgraded to Node.js v6.3.0.

Releases

2017.03.31

  • alpine-nodejs: upgraded to Node.js v6.10.0.
  • alpine-nodejs: upgraded to Node.js v6.10.1.

Releases

2017.03.30

  • alpine-nodejs: upgraded to Node.js v6.9.2.
  • alpine-nodejs: upgraded to Node.js v6.9.3.
  • alpine-nodejs: upgraded to Node.js v6.9.4.
  • alpine-nodejs: upgraded to Node.js v6.9.5.

Releases

2017.03.29

  • alpine-nodejs: upgraded to Node.js v6.9.0.
  • alpine-nodejs: upgraded to Node.js v6.9.1.

Releases

2017.03.23

  • alpine-nodejs: upgraded to Node.js v6.4.0.
  • alpine-nodejs: upgraded to Node.js v6.5.0.
  • alpine-nodejs: upgraded to Node.js v6.6.0.
  • alpine-nodejs: upgraded to Node.js v6.7.0.
  • alpine-nodejs: upgraded to Node.js v6.8.0.

Releases

2017.03.22

  • alpine-nodejs: upgraded to Node.js v6.10.0.

Releases

2017.03.21

  • alpine-nodejs: upgraded to Node.js v6.9.2.
  • alpine-nodejs: upgraded to Node.js v6.9.3.
  • alpine-nodejs: upgraded to Node.js v6.9.4.
  • alpine-nodejs: upgraded to Node.js v6.9.5.

Releases

2017.03.20

  • alpine-nodejs: upgraded to Node.js v6.7.0.
  • alpine-nodejs: upgraded to Node.js v6.8.0.
  • alpine-nodejs: upgraded to Node.js v6.9.0.
  • alpine-nodejs: upgraded to Node.js v6.9.1.

Releases

2017.03.17

  • alpine-nodejs: upgraded to Node.js v6.4.0.
  • alpine-nodejs: upgraded to Node.js v6.5.0.
  • alpine-nodejs: upgraded to Node.js v6.6.0.

Releases

2016.11.12

  • alpine-consul-nodejs: upgraded to Node.js v6.3.1.
  • alpine-nodejs: upgraded to Node.js v6.3.1.
  • alpine-consul: upgraded to Consul v0.7.1.
  • alpine-consul: go-dnsmasq is now run as the go-dnsmasq user.
  • alpine-consul-base: now inherits from alpine-consul:3.1.1.

Releases

2016.10.30

  • alpine-consul-redis: upgraded to alpine-consul-base:4.1.0.
  • alpine-consul-ui: upgraded to alpine-consul:1.1.0.
  • alpine-consul-ui: updated to take advantage of consul-join-wan script and environment variables $CONSUL_RETRY_INTERVAL, $CONSUL_DOMAIN, $CONSUL_DC and $CONSUL_CLIENT. alpine-consul-ui run script is now inline with the alpine-consul run script.
  • alpine-consul-apache: upgraded to alpine-consul-base:4.1.0.
  • alpine-consul-apache: added apk upgrade.
  • alpine-consul-apache: updated to use Consul's built-in HTTP(s) check.
  • alpine-consul-apache: fixed Apache runtime error by adding mkdir -p /run/apache2/ to the Dockerfile.
  • Updated the user-consul-ui example to use Docker Compose.
  • Updated the user-consul-apache example to use Docker Compose. Show's it running with a cluster.

Releases

2016.10.23

  • alpine-consul-nodejs: upgraded to alpine-consul-base:4.1.0.
  • alpine-consul-nginx: upgraded to alpine-consul-base:4.1.0.

Releases

2016.10.21

  • alpine-apache: merged in changes to resolve an issue with Apache quitting.
  • alpine-apache: upgraded to Apache v2.4.23.
  • alpine-base: upgraded go-dnsmasq to v1.0.7 (resolves DNS issues on container restarts janeczku/go-dnsmasq#18).
  • alpine-base: upgraded s6-overlay to v1.18.1.5.
  • alpine-confd: upgraded FROM to alpine-base:3.1.0.
  • alpine-consul: upgraded FROM to alpine-base:3.1.0.
  • alpine-consul: upgraded Consul to v0.7.0.
  • alpine-consul-base: added apk upgrade.
  • alpine-consul-base: upgraded consul-template to v0.16.0.
  • alpine-consul-nodejs: added apk upgrade.
  • alpine-consul-nginx: added apk upgrade.
  • alpine-consul-redis: added apk upgrade.
  • alpine-consul: removed the finish file. This was bringing down the container unnecessarily. If Consul dies, no need to bring down the container. Restart Consul, let it reload the configuration files and attempt to re-join the cluster.
  • alpine-consul: update -dc to -datacenter.
  • examples/complete: adding NODEJS_EXIT to the environment variables for the app service will cause Node.js to exit between 1 minute and 1.5 minutes. This is to simulate nodes going down, to test them rejoining the Consul cluster.
  • Upgraded the Vagrant VM to a new box (based on Ubuntu 16.04). I was running into issues building images which issue setcap (after Docker 1.10, moby/moby#20658). This upgrade has resolved those issues. If you're contributing to docker-alpine, you should destroy your VM and set it up again (after a git pull).

Releases

2016.09.12

  • alpine-confd: upgraded to alpine-base v3.0.0.

Releases

2016.07.28

  • alpine-nginx-nodejs: upgraded Node.js to v6.2.1.
  • alpine-nginx-nodejs: upgraded Node.js to v6.2.2.
  • alpine-nodejs: upgraded Node.js to v6.3.0. Node.js is now compiled without the --fully-static flag allowing dynamic loading.
  • alpine-nodejs: Add apk upgrade --update to the Dockerfile so that APK packages are now updated when the image is built.

Releases

2016.07.27

  • alpine-nginx-nodejs: upgraded Node.js to v6.0.0.
  • alpine-nginx-nodejs: upgraded Node.js to v6.1.0.
  • alpine-nginx-nodejs: upgraded Node.js to v6.2.0.

Releases

2016.07.26

  • alpine-nginx-nodejs: upgrade to the latest version of alpine-nginx.
  • alpine-nginx-nodejs: upgraded Node.js to v5.9.0.
  • alpine-nginx-nodejs: upgraded Node.js to v5.9.1.

Releases

2016.07.22

  • Now using http://dl-4.alpinelinux.org/alpine/v3.3/main APK repository to source v1.8.1 of Nginx in alpine-consul-nginx.

Releases

2016.06.08

  • Updated the examples/user-consul-nodejs to use Docker Compose and zero-conf bootstrapped Consul.
  • Updated the examples/user-consul-nginx to use Docker Compose and zero-conf bootstrapped Consul.
  • Updated the examples/user-consul-nodejs to use Docker Compose and zero-conf bootstrapped Consul.
  • Removed the :dev tags from examples/complete.

Releases

2016.06.07

2016.05.27

  • alpine-consul-base: renamed /usr/bin/container-ip to /usr/bin/host-ip to be more explicit about what it does.
  • alpine-consul-consul: added /usr/bin/container-find which is used to find container IP addresses matching a specific DNS name (by default). This script is used within consul-join. Through adding this script, it is now quite easy to customise host-ip and container-find so that these containers can work in non-standard scenarios (such as Rancher and Docker Cloud). It's easier to overwrite these files which are logic, as opposed to consul-join in which you'd need to recreate the logic.
  • alpine-consul-ui: has been updated to use host-ip rather than container-ip.
  • alpine-consul: now sets CONSUL_SERVER_NAME environment variable and this is used within the container as the name for DNS queries. By default alpine-consul nodes have been setup to use consul as their service name, however, with CONSUL_SERVER_NAME you can now customise this as required.

2016.05.19

  • alpine-consul-base: /etc/services.d/consul-template/finish no longer attempts to bring down the entire container. It is a secondary process and therefore should simply restart.
  • alpine-consul-base: introduced the exec keyword in /etc/services.d/consul-template/run when starting consul-template. It seems to play nicer and can now receive signals such as s6-svc -h /var/run/s6/services/consul-template.

2016.05.18

  • alpine-consul: reverted consul-join to use dig rather than getent hosts so that -retry-join flag will use all available consul IPs to attempt to join. This means container-ip uses getent hosts and consul-join uses dig. This has proven to be the most stable setup across Docker 1.9 and Docker 1.11.

2016.05.17

  • alpine-base: reverted container-ip to use getent hosts rather than dig to determine the container ip. After testing with Docker 1.9 getent hosts is much more stable (essentially until go-dnsmasq is up and running).

2016.05.13

  • General: tagged all builds with :dev and will release these on Docker hub now. Final testing before release.
  • alpine-consul-redis: now inherits from the latest version of alpine-consul-base.
  • alpine-consul-redis: updated to the latest version of Redis 3.2.0. Redis runs with protected mode off assuming that we're running Redis with container-only access and therefore protected mode is not required.
  • General: update the example to add session management via Redis (demonstrating load balancing with sticky sessions).

2016.05.11

  • alpine-consul: customised /etc/services.d/consul/run removing -client $BIND in favour of -advertise $BIND -client 0.0.0.0 so that Consul works in more environments (such as overlay networks or environments with multiple IPs).
  • alpine-consul-base: customer /etc/services.d/consul/run removing -client $BIND in favour of -advertise $BIND -client 0.0.0.0 so that Consul works in more environments (such as overlay networks or environments with multiple IPs).
  • General: updated the example to demonstrate Nginx load balancing to multiple Node.js containers.
  • alpine-consul: /usr/bin/consul-join will now output all consul IPs (excluding itself) with the -retry-join argument (for example -retry-join 172.19.0.7 -retry-join 172.19.0.6) so that Consul can try mutliple IPs.
  • alpine-consul: /etc/services.d/consul/run now accepts the CONSUL_CONFIG_DIR ENV variable for the location of the Consul configuration directory. Set CONSUL_CONFIG_DIR in alpine-consul/Dockerfile.
  • alpine-consul-base: removed /etc/services.d/consul/run and set CONSUL_CONFIG_DIR in alpine-consul-base/Dockerfile.
  • alpine-consul-ui: updated /etc/services.d/consul/run to take advantage of improvements listed above and set CONSUL_CONFIG_DIR in alpine-consul-ui/Dockerfile.

2016.05.10

  • General: moved all temporary scripts created in the images in examples/complete back into their respective docker-alpine containers (for example container-ip, consul-join, consul-available and all run scripts).
  • alpine-consul-nginx: fixed issues in which the container assumed an incorrect default root.
  • alpine-consul-nginx: moved to the built-in http Consul check replacing the shell script based version we had.
  • General: reduced output from consul-available script. It would unnecessarily print an IP to stdout.
  • alpine-consul: now expects to be bootstrapped with three other nodes as the default.
  • alpine-consul-base: all images extending alpine-consul-base will now automatically join a Consul cluster.
  • General: removed the examples/complete/consul container as it can now be done in just a few lines in the docker-compose.yml. Bootstrapping a multi-node Consul cluster is so simple now! FTW!
  • General: removed the examples/complete/consului container as it can now be done in just a few lines in the docker-compose.yml (an entire container just for the UI is no longer required).

2016.05.04

  • General: Create a container-ip script that will be used in all other scripts when the IP of the container is required. This will make it easy to override this function in just one place (#41). Lives here in alpine-base.
  • alpine-base: go-dnsmasq has been updated to 1.0.4.
  • alpine-base: --append-search-domains flag has been removed from go-dnsmasq start. This was because Docker 1.10+ seems to add localdomain as a search domain to /etc/resolv.conf and makes queries longer.
  • alpine-base: --ndots "1" --fwd-ndots "0" flags have been added to go-dnsmasq start. These have been added because Docker 1.10+ adds options ndots:0 to /etc/resolv.conf and go-dnsmasq requires a setting of 1. And --fwd-ndots "0" instructs go-dnsmasq to forward queries to domains without dots (i.e. consul as we do now) to upstream DNS servers.
  • Consul-related: -retry-interval has been reduced from 15s to 5s.

2016.05.02

  • General: Docker Engine has been updated to 1.11 (run (on host) vagrant destroy && vagrant reload --provision).
  • Consul-related: examples/complete/consul, examples/complete/consul-ui, examples/complete/static were all updated to enable zero-conf Consul bootstrapping.

2016.04.28

  • alpine-consul-base: no longer restarts the container if Consul fails. s6 simply restarts Consul.
  • Consul-related: leave_on_terminate has been removed from Consul configuration files.
  • Consul-related: remove exec from start scripts as this was interfering with signals and proper shutdown order.
  • alpine-consul-base: now issues -bind and -client when starting Consul such that all Consul interfaces are being bound to the IP of the container not localhost (this change means that a query to any Consul interface originating externally from the container itself can be used).
  • alpine-consul-ui: now issues -client when starting Consul.
  • alpine-consul: the cont-finish.d/00-consul script in alpine-consul now issues the consul leave command rather than consul force-leave and provides the -rpc-addr flag because we've moved away from the default of localhost. Removing exec from the Consul start scripts has made this possible as the scripts in cont-finish.d are run prior to the service directory finish scripts. This has made leaving the Consul cluster much, much, much more consistent.
  • alpine-consul: now distinguishes between exiting because of CTRL+C (while developing) and a crash of the Consul process (you can simulate with kill -9 <pid>). When exiting because of CTRL+C the attempt to bring down the container is not made as this is already happening. This has tidied up the s6-svscanctl: fatal: unable to control /var/run/s6/services: supervisor not listening error.
  • go-dnsmasq-related: go-dnsmasq has been updated as the Consul DNS service is no longer bound to localhost but the IP of the container instead.
  • General: preferring $VARNAME syntax over ${VARNAME} in shell scripts.
  • Development: Docker Compose was updated to 1.7.0 (run (on guest) sudo rm /etc/vagrant/compose and then (on host) vagrant reload --provision) to upgrade.