mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 17:35:52 +03:00
[GH-ISSUE #67] Unable to build locally using 'docker build' from latest release #66
Labels
No labels
awaiting feedback
bug
cannot reproduce
dns provider request
duplicate
enhancement
enhancement
enhancement
good first issue
help wanted
invalid
need more info
no certbot plugin available
product-support
pull-request
question
stale
troll
upstream issue
v2
v2
v2
v3
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nginx-proxy-manager-NginxProxyManager#66
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @binhex on GitHub (Feb 7, 2019).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/67
Hi, currently its not possible to build a new docker image from what is on github, if you pull down the latest release (or branch master) and then attempt a docker build you will see missing files used in the build, output:-
Step 9/21 : ENV NODE_ENV=production ---> Running in 0ae14e229c19 Removing intermediate container 0ae14e229c19 ---> f483986396ed Step 10/21 : ADD dist /app/dist ADD failed: stat /var/lib/docker/tmp/docker-builder216809384/dist: no such file or directoryso im assuming that all files ADDed at build time are not currently on github, any chance you could push these up please.
@alaszlotrend commented on GitHub (Feb 13, 2019):
Have you tried to install the npm deps and build the application?
I've just pulled down the latest and code and seems to be working
@binhex commented on GitHub (Feb 13, 2019):
i downloaded latest master branch and used the included Dockerfile to attempt build, according to some of the comments in the Dockerfile it should have all included dependencies from the base image used.
if those dependencies should be built as part of the build of the image then i would expect to see them included in the Dockerfile to be honest, as it stands its not really complete at the moment.
i will have a further play, thanks for the comment.
@jc21 commented on GitHub (Feb 18, 2019):
Take a look at the CI script,
Jenkinsfilefrom line 64 to 71. You can ignore any commands using the$DOCKER_CI_TOOLSimage, it's just a docker container with some helper commands.Reopen if you still have problems.