Allow an explicit Dockerfile location string to be specified to the build command #825
Conversation
This file contains hidden or 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
…want to pass a String location of the Dockerfile within the TAR stream they are supplying
Codecov Report
@@ Coverage Diff @@
## master #825 +/- ##
==========================================
+ Coverage 71.73% 71.75% +0.02%
==========================================
Files 306 306
Lines 6587 6592 +5
Branches 484 485 +1
==========================================
+ Hits 4725 4730 +5
Misses 1577 1577
Partials 285 285
Continue to review full report at Codecov.
|
KostyaSha
requested changes
Apr 4, 2017
Member
KostyaSha
left a comment
KostyaSha
left a comment
There was a problem hiding this comment.
missing netty test com.github.dockerjava.netty.exec.BuildImageCmdExecTest
…ocation within a tar
Contributor
Author
|
Added a netty test |
vuminhkh
added a commit
to alien4cloud/docker-java
that referenced
this pull request
Apr 30, 2017
* master-docker-java: (25 commits) Add some coding styles. Allow an explicit Dockerfile location string to be specified to the build command (docker-java#825) Proposed fix for docker-java#830 (docker-java#832) [maven-release-plugin] prepare for next development iteration [maven-release-plugin] prepare release 3.0.9 Fix test. Update CHANGELOG.md Responce may contains token. adding support for unless-stopped restart policy Generate OSGi compliant manifest (docker-java#797) exclude commons-logging since docker-java uses slf4j/logback Unable to deserialize status response from amazon ECR login Ensure FakeDockerServer is started on a random free port Fixes docker-java#807. NettyDockerCmdExecFactory ignores API version configuration [maven-release-plugin] prepare for next development iteration [maven-release-plugin] prepare release 3.0.8 Update CHANGELOG.md Added healthcheck support in container inspect JSON result Use TLSv2 by default rerun failing tests count to 3 ... # Conflicts: # pom.xml
panuse
pushed a commit
to TuKangTech/docker-java
that referenced
this pull request
Aug 20, 2017
…uild command (docker-java#825) * When supplying a TAR stream to the build command, API consumers just want to pass a String location of the Dockerfile within the TAR stream they are supplying * Add netty test for building with an explicitly specified Dockerfile location within a tar
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
When supplying a tar stream to the build command, API consumers just want to pass a String location of the Dockerfile within the tar stream they are supplying
This change is