From to ~edwardloveall/scribe
Dear Edward, I'm terribly sorry! I missed the parameters in my last email. In line 6, it should be as follows. (The current file still builds, but the parameters are nice to have.) yarn install --network-timeout 120000 --no-progress --frozen-lockfile Sorry again, O 2023年11月27日 02:02 來自 edward@edwardloveall.com: > Great! It is now merged to main. > > Edward >
From to ~edwardloveall/scribe
Dear Edward, The changes are right, and I verified that the Dockerfile builds in both amd and arm architecture. Thanks! Best, O Nov 25, 2023, 06:39 by edward@edwardloveall.com: > Hi O, > > I just pushed your suggestions to the el-docker-updates branch. Can you verify that it's what you expected? >
From to ~edwardloveall/scribe
Dear Edward, Sorry to bother you again. `Dockerfile.arm64`, which I proposed last month, builds fine. However, Lomanic, a fellow maintainer, suggested an even better method to build a multi-arch Docker image. It requires only one Dockerfile in your tree. The method involves replacing `crystallang/crystal:1.8.1-alpine` with the multi-arch base image `84codes/crystal:1.8.1-alpine`. And adding the line `RUN yarn install --network-timeout 120000` to work around yarn issues. Please reference Lomanic's Gitlab workflow below (Specifically line 41-42) https://gitlab.com/Lomanic/scribe-binaries/-/blob/master/.gitlab-ci.yml?ref_type=heads The third party base image is open-source and clean. https://github.com/84codes/crystal-container-images I believe this is a better approach, as it saves you from maintaining `Dockerfile.arm64 <https://git.sr.ht/~edwardloveall/scribe/tree/main/item/Dockerfile.arm64>`and its dependencies.
From to ~edwardloveall/scribe
Dear Edward, Thank you! It works as intended now. Sorry I'm unfamiliar with the sourcehunt mailing list and made some mistakes. Best, O Oct 13, 2023, 08:19 by edward@edwardloveall.com: > Ah I see. I think your initial message was missing a newline around the FROM and I thought you were saying I should remove that line. I just committed it back to the branch and pushed it up. It should now match your example Dockerfile (thank you for that, BTW). >
From to ~edwardloveall/scribe
Hi Edward, Thanks for the swift reply. In my testing, "FROM alpine:3.18.4 AS lucky_build" need to be added after "RUN yarn prod", the build process fails otherwise with the following error: invalid from flag value node_build: pull access denied for node_build, repository does not exist or may require 'docker login': denied: requested access to the resource is denied A working dockerfile.amd64 can be found here: https://b.opnxng.com/?a1098a94417264d9#8KaJpcSxpgfb7k4SQewtJ2xcnJf8w4LeDh38RZNvwApQ (Tested on my instance m.opnxng.com <http://m.opnxng.com>.) Thank you! Oct 11, 2023, 07:47 by edward@edwardloveall.com: > Hi opnxng,
From to ~edwardloveall/scribe
Hi, Would you please consider adding a separate Dockerfile.arm64? Network timeouts and the lack of a crystallang base image are two main issues on ARM. They can be solved by changing the following lines. Thanks! # RUN yarn install --no-progress --frozen-lockfile RUN yarn install --network-timeout 120000 --no-progress --frozen-lockfile # FROM crystallang/crystal:1.5-alpine as lucky_build FROM alpine:3.18.4 AS lucky_build RUN apk add --no-cache 'crystal=1.8.2-r0' shards sqlite-static yaml-static yaml-dev libxml2-dev zlib-static openssl-libs-static openssl-dev musl-dev
From to ~edwardloveall/scribe
Hi, Would you please consider adding a separate Dockerfile.arm64 <https://github.com/zedeus/nitter/blob/master/Dockerfile.arm64>? Network timeouts and the lack of a crystallang base image are two main issues on ARM. They can be solved by changing the following lines. Thanks! # RUN yarn install --no-progress --frozen-lockfile RUN yarn install --network-timeout 120000 --no-progress --frozen-lockfile # FROM crystallang/crystal:1.5-alpine as lucky_buildFROM alpine:3.18.4 AS lucky_build RUN apk add --no-cache 'crystal=1.8.2-r0' shards sqlite-static yaml-static yaml-dev libxml2-dev zlib-static openssl-libs-static openssl-dev musl-dev
From to ~cadence/breezewiki-discuss
Hello, The docker image by Pussthecat.org is great, but it doesn't work for ARM64. If anyone is interested. I have wrote the Dockerfile and built an ARM64 image on my registry. (It works by installing racket via the arm64 debian repo.) Thanks. https://gitlab.com/opnxng/breezewiki/container_registry Best, O
From to ~cadence/breezewiki-discuss
Hello,Would you please the following new mirror? Thank for your work!Hoster: Opnxng https://about.opnxng.com/Link: https://z.opnxng.com/Subdomain support is also working.Best,Opnxng
From to ~cadence/breezewiki-discuss
Hello, Subdomain support is working now too! > Hello, > Would you please the following new mirror? Thank for your work! > > Hoster: Opnxng > https://about.opnxng.com/ > Link: > https://z.opnxng.com/ > > Subdomain support is not working at the moment. Will implement it once I figure out the caddy configs. >