Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Unable to use Alpine version anymore #3

Closed
jaymoulin opened this issue Dec 3, 2022 · 0 comments
Closed

Unable to use Alpine version anymore #3

jaymoulin opened this issue Dec 3, 2022 · 0 comments
Assignees
@jaymoulin
Labels
bug Something isn't working

Comments

@jaymoulin
Copy link
Member

Due to this issue nodejs/docker-node#1589, I'm not able to maintain as an alpine image.

I'll rollback to alpine when fixed
@jaymoulin jaymoulin added the bug Something isn't working label Dec 3, 2022
@jaymoulin jaymoulin self-assigned this Dec 3, 2022
jaymoulin added a commit that referenced this issue Dec 22, 2022
@jaymoulin
related #3 - Rollback alpine version
25cc56f 
unable to build due to buggy libseccomp2 cross compilation preventing
alpine build for armhf/armv6. Nothing found so far...
@jaymoulin jaymoulin reopened this Dec 22, 2022
jaymoulin added a commit that referenced this issue Dec 23, 2022
@jaymoulin
related #3 - Rollback alpine version
3064bcc 
unable to build due to buggy libseccomp2 cross compilation preventing
alpine build for armhf/armv6. Nothing found so far...
jaymoulin added a commit that referenced this issue Dec 23, 2022
@jaymoulin
related #3 - Rollback alpine version
b1072a0 
unable to build due to buggy libseccomp2 cross compilation preventing
alpine build for armhf/armv6. Nothing found so far...
jaymoulin added a commit that referenced this issue Apr 24, 2024
@jaymoulin
Unable to build on previous version - may affect #3
7a50ec8
jaymoulin added a commit that referenced this issue May 1, 2024
@jaymoulin
Moved from manifest to buildx
7ed56c3 
Also, this needed to rollback node image to 18 due to nodejs/docker-node#1829
This may have implications on #3.

The image still install latest available eleventy from NPM, so each beta
build is just another latest stable. This issue is due to process
between github-release-notifier and eleventy team making a tag on github
on each beta build. This should be handled by github-release-notifier
jaymoulin added a commit that referenced this issue May 2, 2024
@jaymoulin
Moved from manifest to buildx
3a9e35d 
Also, this needed to rollback node image to 18 due to nodejs/docker-node#1829
This may have implications on #3.

The image still install latest available eleventy from NPM, so each beta
build is just another latest stable. This issue is due to process
between github-release-notifier and eleventy team making a tag on github
on each beta build. This should be handled by github-release-notifier
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jaymoulin jaymoulin

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jaymoulin