Don't lock source when building in a container
The container build process can work independently of the source, so no locking is required. (this also fixes unprivileged container builds)pull/34356/head
parent
d1fe3b1cf6
commit
100aff90d7
3
Makefile
3
Makefile
|
@ -77,8 +77,9 @@ container-push: container-image ## Push container image for the preview of the w
|
|||
container-build: module-check
|
||||
$(CONTAINER_RUN) --read-only --mount type=tmpfs,destination=/tmp,tmpfs-mode=01777 $(CONTAINER_IMAGE) sh -c "npm ci && hugo --minify --environment development"
|
||||
|
||||
# no build lock to allow for read-only mounts
|
||||
container-serve: module-check ## Boot the development server using container.
|
||||
$(CONTAINER_RUN) --cap-drop=ALL --cap-add=AUDIT_WRITE --read-only --mount type=tmpfs,destination=/tmp,tmpfs-mode=01777 -p 1313:1313 $(CONTAINER_IMAGE) hugo server --buildFuture --environment development --bind 0.0.0.0 --destination /tmp/hugo --cleanDestinationDir
|
||||
$(CONTAINER_RUN) --cap-drop=ALL --cap-add=AUDIT_WRITE --read-only --mount type=tmpfs,destination=/tmp,tmpfs-mode=01777 -p 1313:1313 $(CONTAINER_IMAGE) hugo server --buildFuture --environment development --bind 0.0.0.0 --destination /tmp/hugo --cleanDestinationDir --noBuildLock
|
||||
|
||||
test-examples:
|
||||
scripts/test_examples.sh install
|
||||
|
|
Loading…
Reference in New Issue