mini-containers / base Goto Github PK

Curious about two things:

• Why running on edge? Edge is broken for at least mysql-client (my test case for mini/base was a super small MySQL client). However, that works fine when rebuilt on v3.1.
• Why extra layers for maintainer and apk upgrade? The upgrade would be better left to the user if they wanted to. Not sure if there is a need to upgrade assuming you just build the image. Also, adding extra layers for stuff like MAINTAINER seems kind of against the spirit of something trying to be minimal.

Just my $0.02. I'd love to try and use this as my go to for minimal containers. But don't really want to really on edge and would much prefer a base on stable or even better, tags to choose my version.

I'd be happy to make a pull request if you agree on these points. Thanks for your work on this so far!

http://alpinelinux.org/posts/Alpine-3.4.0-released.html

Hi, I'm trying to use mini/base to create a minimal-nvm container. see this Dockerfile:

FROM mini/base

RUN apk-install \
      bash \
      tar \
      curl \
      git \
      c-ares \
      libgcc \
      libstdc++ \
      libuv

RUN rm /bin/sh && ln -s /bin/bash /bin/sh && \
    touch ~/.bashrc

ENV NODE_VERSION iojs

RUN NVM_VERSION="$(curl -s -L http://latest.nvm.sh -o /dev/null -D - | grep -Ei '^Location: .*tag/v[0-9.]+' | grep -oEi 'v[0-9.]+')" && \
    echo $NVM_VERSION && \
    curl https://raw.githubusercontent.com/creationix/nvm/$NVM_VERSION/install.sh | sh && \
    source ~/.nvm/nvm.sh && \
    nvm install $NODE_VERSION

when running:

→ docker run --rm -it mini-nvm bash

bash-4.3# nvm run iojs -p process.versions
Running io.js v1.5.1
bash: /root/.nvm/versions/io.js/v1.5.1/bin/iojs: No such file or directory

bash-4.3# ls -la /root/.nvm/versions/io.js/v1.5.1/bin/iojs
-rwxrwxr-x    1 500      500       16545561 Mar  9 18:14 /root/.nvm/versions/io.js/v1.5.1/bin/iojs
kriswill 12 hours ago  

Any advice is appreciated!