-
Notifications
You must be signed in to change notification settings - Fork 46
[IMP] Switch to ash #189
Comments
Alpine use busybox and adds 900kb of memory per running instance, I propose to use dash for shell in docker images |
Well I think I understand why @lasley suggest Personal preference, I don't really like the user experience when I'm in the container but that's mainly because I'm too much attached to bash. No real reason then. When we feel ready, we mainly have to remove bash from base image Propose your best shell for alpine use and let's vote. |
Yeah the only reason I proposed |
Yep, that said a shell doesn't take much space and it's something really convenient. We should vote for the best user experience, for our own sake. For execution, I think we should use either |
Yeah really here I was referring more to execution and not the use. You're probably right with So we would basically just want the user shell in the I like bash personally in terms of experience, but it's a bit heavy. cc @tedsalmon |
Not only ssh-exec, we often connect to any kind of container through Same for me with bash. Alpine with bash take 1.5Mo http://www.blang.io/posts/2015-04_how-to-build-the-smallest-docker-containers/, clearly not a problem (remember the 200Mo ubuntu image?). |
I agree that |
Hmmm ok so lack of arrays is really setting me back here. I took a look at dash too, and it seems that wouldn't provide either. What are your thoughts? Do we have another solution for an array like structure? The thing that's killing me is the SC2086 - Double quote to prevent globbing and word splitting Lint, which I can't totally argue with. But that makes something as simple as:
turn into a real pain. Well or disabling the lint, but I honestly don't consider that an option. |
I noticed that we have bash pretty engrained into the templates and whatnot. Now that we're using Alpine, we should switch up to
ash
instead so that we're not installing another dependency.This ticket is for the discussion and tracking of that effort.
The text was updated successfully, but these errors were encountered: