Hello,

The docker images on docker-hub are based on Debian stretch, they are not as
stripped down as what we use for the matrix build, as I think it nice to have at
least some tools around. Anyway if you have a specific dev scenario in mind, I
guess we should just rewrite the Dockerfile and setup a Jenkins job that builds
everything once there is a new release and a nightly version would be great as
well.

Thanks,
Marcus

Here is the Dockerfile I used:

FROM mlpack/templates:mlpack-stretch-27-template

# Meta information.
LABEL maintainer="[email protected]"

# Get mlpack version.
ARG mlpack_archive

# Update software repository, install dependencies and build mlpack.
RUN useradd -m mlpack && echo "mlpack:mlpack" | chpasswd && \
    adduser mlpack sudo && su mlpack && cd /home/mlpack/ && \
    wget -O mlpack.tar.gz ${mlpack_archive} && \
    tar -xvzpf mlpack.tar.gz && cd * && mkdir build && \
    cd build && cmake .. && make -j4 && make install && chown -R mlpack:mlpack 
/home/mlpack

ENV PROJ_WORK_DIR /home/mlpack/build/

# Setup environment.
ENV LD_LIBRARY_PATH /usr/local/lib/
USER mlpack
WORKDIR /home/mlpack
CMD /bin/bash



> On 1. Nov 2019, at 12:12, Ryan Birmingham <[email protected]> wrote:
> 
> Hi Marcus,
> 
> Which scripts are/were used to generate these dockerhub images? Was it 
> https://github.com/mlpack/jenkins-conf/tree/master/Generate%20Dockerfile 
> <https://github.com/mlpack/jenkins-conf/tree/master/Generate%20Dockerfile> ? 
> Are we rebuilding the same dockerfiles from 
> https://github.com/mlpack/jenkins-conf/tree/master/Dockerfiles 
> <https://github.com/mlpack/jenkins-conf/tree/master/Dockerfiles> ? Or is this 
> something else entirely?
> 
> Also, what I'm looking to create or use is a dev container/vm (i.e. a 
> container that can build/test mlpack/ensmallen); maybe that would be a useful 
> tag to add, provided that this setup is useful to people who aren't me :)
> -Ryan Birmingham
> 
> 
> On Thu, Oct 31, 2019 at 1:40 PM Marcus Edel <[email protected] 
> <mailto:[email protected]>> wrote:
> Hello,
> 
> for docker there is
> https://cloud.docker.com/repository/docker/mlpack/mlpack/tags 
> <https://cloud.docker.com/repository/docker/mlpack/mlpack/tags> which should
> provide a docker image for each release and nightly build as well. I have to
> check why the script stopped working.
> 
> Maybe it makes sense to embed the process into a Jenkins job.
> 
> Also maybe we should think about providing a virtualbox image as well?
> 
> Thanks,
> Marcus
> 
> > On 31. Oct 2019, at 16:45, Ryan Curtin <[email protected] 
> > <mailto:[email protected]>> wrote:
> > 
> > On Thu, Oct 31, 2019 at 11:39:35AM -0400, Ryan Birmingham wrote:
> >> Hello everyone,
> >> 
> >> One of the things that I think would be useful to me, at the least, is a
> >> vm/docker/some other thing that I could use as a development environment.
> >> Before I do any work on this, I essentially have two questions: has anyone
> >> else already solved this, and (if not) what would be useful features to
> >> include in a prepackaged dev environment?
> > 
> > Hey Ryan,
> > 
> > Agreed!  I think that could be useful.  This has been discussed about
> > the benchmarks repository:
> > 
> > https://github.com/mlpack/benchmarks/pull/135 
> > <https://github.com/mlpack/benchmarks/pull/135>
> > 
> > But it could definitely be useful for the main mlpack repository too.
> > 
> > If you worked on this, perhaps we could put the Dockerfile in some
> > mlpack repository, and then upload it to DockerHub and update our
> > documentation?  Anyway, just an idea. :)
> > 
> > Hope this helps!  And it was cool to run into you at the GSoC mentor
> > summit in Munich. :)
> > 
> > Ryan
> > 
> > -- 
> > Ryan Curtin    | "Why is it that the landscape is moving... but the boat is
> > [email protected] <mailto:[email protected]> | still?"  - Train Driver
> > _______________________________________________
> > mlpack mailing list
> > [email protected] <mailto:[email protected]>
> > http://knife.lugatgt.org/cgi-bin/mailman/listinfo/mlpack 
> > <http://knife.lugatgt.org/cgi-bin/mailman/listinfo/mlpack>
> 

_______________________________________________
mlpack mailing list
[email protected]
http://knife.lugatgt.org/cgi-bin/mailman/listinfo/mlpack

Reply via email to