Skip to content
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

Make tinet build (buildfile option) work #80

Merged
merged 1 commit into from
Jan 18, 2022

Conversation

YutaroHayakawa
Copy link
Contributor

Currently when we set "buildfile: Dockerfile" and "image: foo:latest"
node options, tinet build produces following command.

docker build -t foo:latest Dockerfile

There are several missing stuff in here. First it needs -f option to
specify Dockerfile path. And second, it doesn't have build context (e.g.
.). Overall, the correct command should look like this.

docker build -t foo:latest -f Dockerfile .

First issue can be solved by adding missing -f option. However, for the
second issue, we don't have any way to specify build context in current
manifest. Thus, this commit adds new node option "buildcontext" as well.

Signed-off-by: Yutaro Hayakawa yhayakawa3720@gmail.com

Currently when we set "buildfile: Dockerfile" and "image: foo:latest"
node options, `tinet build` produces following command.

docker build -t foo:latest Dockerfile

There are several missing stuff in here. First it needs -f option to
specify Dockerfile path. And second, it doesn't have build context (e.g.
.). Overall, the correct command should look like this.

docker build -t foo:latest -f Dockerfile .

First issue can be solved by adding missing -f option. However, for the
second issue, we don't have any way to specify build context in current
manifest. Thus, this commit adds new node option "buildcontext" as well.

Signed-off-by: Yutaro Hayakawa <yhayakawa3720@gmail.com>
@slankdev slankdev merged commit 675cf65 into tinynetwork:master Jan 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants