-
Notifications
You must be signed in to change notification settings - Fork 13
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
[OPS-8056] xz sure why not #292
base: main
Are you sure you want to change the base?
Conversation
…s no longer an exception and also the version is in the filename.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me.
The content of the archive doesn't seem to contain what is needed (ex: '/init').
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like they separated the content into at least 2 mandatory packages: https://github.com/just-containers/s6-overlay#quickstart:
s6-overlay-noarch-$VERSION-tar.xz
s6-overlay-$ARCH-$VERSION-tar.xz
Co-authored-by: orakili <[email protected]>
Welp, poopie. Thanks for the fix :-) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That seems ok now but it would be good to have someone else test as well to confirm.
Issues with nginx (ex: php-k8s images) and s6.
Sorry, dismissing my review again. While the images based on this That may not be an issue withe s6-overlay but I need to investigate more... Advice: read the https://github.com/just-containers/s6-overlay README.md because they changed a lot of things in 3.0.0.0 and it looks like all the |
It does say "We encourage you to switch to the new format, but if you don't need its benefits, you can stick with regular service directories in /etc/services.d, it will work just as well." so nothing breaking there, right? |
That's what they say but in practice, even with the "compatibility" assets mentioned in the installation section: https://github.com/just-containers/s6-overlay#installation, I could not get any images with nginx to listen the ports. But maybe I broke something else. |
I did a build and I think I see the problem, the run scripts aren't executable. Fixing and re-testing. |
And all the helper scripts are now in /package/admin/s6/* and symlinked from /command. So the run scripts will indeed all need updating. Sigh. |
…ts due to bot rate limiting. (#291)
…s no longer an exception and also the version is in the filename.
Co-authored-by: orakili <[email protected]>
…rrect interpreter.
And annoyingly v3 overwites any PATH value to try to pass via an env var. That breaks all our stacks (they need /srv/www/vendor/bin) and I don't want to dump that in the new global config file either, so I've included a hacked up In the mean time, the current HEAD of this branch should be able to build you a working Raspberry Pi image. |
…/docker-images into cafuego/ops-8056-xz-sure-why-not
For NodeJS, I just grabbed the v2.2.0.3 os s6-overlay and thats that. I don't think it's worth the time to rewrite all the stratup scripts and locations just for the sake of running s6-overlay v3.x. |
That's going to create issues as well if the scripts are mapped from the docker compose stack. Probably a better approach to add a pre-init script to make those |
Note, they are probably going to change the URLs again and remove the version from the filenames: just-containers/s6-overlay#386 (comment). |
No description provided.