-
Notifications
You must be signed in to change notification settings - Fork 159
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
haproxy:2.9-alpine can not build #189
Comments
When I set the USER as root and built the image, this time I came accross the following error
It turns out that in reqadd X-Forwarded-Proto:\ http
reqadd X-Forwarded-Proto:\ https to http-request set-header X-Forwarded-Proto http
http-request set-header X-Forwarded-Proto https as explained here |
Ran into the same issue and posted my solution on the OpenBalena forum. I modified the Dockfile to to only temporarily switch to the root user as running a container as root is considered a bad practise. FROM haproxy:2.9.6-alpine
VOLUME [ "/certs" ]
# Switch back to root to install packages
USER root
RUN apk add --update inotify-tools
# Make haproxy user owner of certificate directory (is root by default)
RUN chown haproxy:haproxy /etc/ssl/private
# Switch back to haproxy user
USER haproxy
COPY haproxy.cfg /usr/local/etc/haproxy/haproxy.cfg
COPY start-haproxy.sh /start-haproxy
CMD /start-haproxy https://forums.balena.io/t/logbackend-server-responded-with-status-code-504-mystery-solved/369223/10 |
We've recently updated the project, try it here. |
Hello all,
Starting from a fresh install and build, I am unable to build the Docker containers. Here is a partial output of
./scripts/compose up -d
;I noticed that there was a recent commit #172 has updated the Dockerfile. Once I manually downgraded the version to 1, I was able to successfully build it.
I went ahead and pulled the image and was also unable to run the command manually. It looks like
apk
needs to be run as root. I believe haproxy image uses the user haproxy. So maybe addingUSER root
to the Dockerfile may be a solution. However I am not sure how everything else may be effected.The text was updated successfully, but these errors were encountered: