Be notified of new releases
Create your free GitHub account today to subscribe to this repository for new releases and build software alongside 28 million developers.Sign up
Recent versions of Docker for Mac support cached volume mounting for wildly reduced filesystem I/O time. Binci 5.4.0 now uses cached mode automatically when mounting the local project folder. Volumes specified in the binci.yml can, as always, include the new
:delegated directives at the end of the path in the same way they would be used on the CLI at the user's discretion.
For those who have Binci set to build containers from a Dockerfile, changes to the Dockerfile have always triggered a rebuild. But what about files like dependency lists that can change what goes into your built image without altering the Dockerfile? You end up running your code on the same old container without the new dependencies, and errors abound.
Today's release fixes that with the rebuildOnChange key. Simply specify a list of files that should cause a rebuild the new time a binci task is run if they get changed:
dockerfile: ./Dockerfile rebuildOnChange: - requirements.txt
Now, when requirements.txt is updated either by you or by a git pull, the next
binci task you run will rebuild your container first.
Binci can now automatically tag images that it builds from a Dockerfile. This allows images to be immediately run, pushed, extended, or reused after a binci command causes it to be built, without requiring a rebuild.
Binci now automatically detects whether or not it's running in a TTY, and launches docker with the appropriate interactive/TTY flags. This allows execution in environments where a TTY is not available, without resorting to screen or tmux hacks.
Fixes generated output from
binci init command:
- before: - - echo "before..." - after: - - echo "after..." + before: | + echo "before..." + after: | + echo "after..."