You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the solution you'd like
Implement a docker-compose.yml file to run the build "app" service and run the application as a docker container. Set a volume host to the project root to map all the changes from the project to the docker container. Make sure the server is restarted inside the docker container on every file change.
The text was updated successfully, but these errors were encountered:
I've worked with goreleaser a few times to publish docker containers as part of the release process. I didn't originally find it straightforward, but ultimately was satisfied with the results. The goreleaser philosophy does the full build once, outside the container and then expects to copy the binaries from an earlier step into the container. This negates the need for multi-stage builds and encourages consistency at the binary level. It also sets up the context for the docker build within the dist/ directory as appropriate for the architecture.
If useful, I can add this content to a PR or add more details.
Changes requried include two files. The first adds a dockers stanza to the .goreleaser.yaml file and a the second is a dedicated Dockerfile for the release. Here's an example of both:
FROM cgr.dev/chainguard/wolfi-base
RUN apk add --no-cache tini bash
# These arguments can be overriden when building the image
ARG IAM_DIR=/tmp/vgw
ARG SETUP_DIR=/tmp/vgw
RUN mkdir -p $IAM_DIR
RUN mkdir -p $SETUP_DIR
# nobody 65534:65534
USER 65534:65534
VOLUME "/data"
EXPOSE 7070
COPY versitygw /versitygw
CMD [ "/versitygw", "posix", "/data"]
ENTRYPOINT [ "/sbin/tini", "--" ]
Describe the solution you'd like
Implement a docker-compose.yml file to run the build "app" service and run the application as a docker container. Set a volume host to the project root to map all the changes from the project to the docker container. Make sure the server is restarted inside the docker container on every file change.
The text was updated successfully, but these errors were encountered: