-
Thanks for the feedback. Do you mean when property
Build Pathis specified, OneDev should default dockerfile to be<Build Path>/Dockerfileif propertyDockerfileis not specified?Also if
Build Pathis specified, can you please let me know why need to append a.after the path? I tested and it does not make any difference. -
Name Previous Value Current Value Type
Improvement
Bug
Seen Builds
empty 4516
-
OK. This is actually a bug, the build path is not taking effect.
-
Previous Value Current Value Docker build image
Docker build image build path not taking effect
-
OneDev
changed state to 'Closed' 3 years ago
Previous Value Current Value Open
Closed
-
OneDev
changed state to 'Released' 3 years ago
Previous Value Current Value Closed
Released
-
State changed as build #3135 is successful
-
thanks to have toake a look, Yes it was look like Build Path take no effect.
But im general i use the final Dot "." for change my working directroy.
Exemple: ./alpine/Dockerfile ./debian/Dockerfile
Without touch Dockerfile name or Build Path, inside my CI/CD i build like that.
docker build ./alpine/. docker build ./debian/.in general i just change the Dot context . in ny exemple i can continue to use **-f ** option and plsy with de Build Path.
Brief thanks for you assistance i'll test the version 7.7.14 ASAP.
OneDev will change the world !!!
Regards
-
With 7.7.14, the behavior will be the same as docker command, ie. just change build path and OneDev will look for Dockerfile under that build path without specifying Dockerfile property.
| Type |
Bug
|
| Priority |
Normal
|
| Assignee | |
| Affected Versions |
Not Found
|
Context
I run 1dev/server, 1dev/agent and registry2 . I have succes fully build my own Docker Image by use "Execute Commands" But i got trouble with **Build Docker Image **
The Trouble
Impossible to got directories structure inside my project to store differente Dockerfile , in fact the "Build Path" entry have no sense to me.
the famous "." at the end of a "docker build" is not optional and dont mean "./", it make reference of a file call "." in each directory. Then for change the "." context you set "PATH/." (with a . at end)
By exemple:
Summary
I suppose "Build path" is a reference to PATH from docker help build where the default is PATH/Dockerfile. Unfortunally to me, that is not possible to change the "." path (like "./alpine/3/.") and that force me to play with the Dockerfile name , where i prefert juste change the "." location
Proposal