-
Notifications
You must be signed in to change notification settings - Fork 156
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
Pass arch to docker #63
base: master
Are you sure you want to change the base?
Conversation
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.
I'm not a maintainer but have contributed a bunch here. Just some suggestions for consistency with the surrounding code.
Thanks @danhunsaker, sorry for the late response but I'm a bit low on time lately. |
No rush. The folks over at the archarm repo still haven't responded, so you're doing better than they are. 😁 |
@uraimo just a heads up, I'm attending to some personal matters and likely won't have time to review PRs here for at least a month. |
@elijahr sure don't worry, everything else comes first. |
hi there! any chance we could get this to work? |
This PR does a couple of things. Primarily, it passes the target architecture to the various Docker commands so that it will stop complaining about not being told in advance. (resolves #21). Secondarily, it groups output lines for easier debugging and suchforth (resolves #62).
As an added bonus, it switches to a fork of archarm with more recent images, which solves the issue seen in testing and downstream use cases where a full system upgrade refuses to complete due to insufficient storage space (resolves #48). This part is expected to be reverted once the upstream merges agners/archlinuxarm-docker#8 and their own builds resume, but who knows how long that might take. The expected reversion is why it's in its own commit, here.