[Mailman-Developers] Docker files for mailman

[Danil Smirnov]

Hi Simon!

I've just tried to build docker image from the Dockerfile mentioned on page
https://wiki.list.org/DEV/Mailman%203.0/Mailman%203.0%20Suite%20Dockerfile

The building has stopped with the following error

Installing mailman.
> The executable python3.4 (from --python=python3.4) does not exist
> /tmp/tmpez1ftK/run: 2: /tmp/tmpez1ftK/run:
> /mailman3/mailman-bundler/venv-3.4/bin/pip: not found
> While:
>   Installing mailman.
>
> An internal error occurred due to a bug in either zc.buildout or in a
> recipe being used:
> Traceback (most recent call last):
>   File "/usr/local/lib/python2.7/dist-packages/zc/buildout/buildout.py",
> line 1995, in main
>     getattr(buildout, command)(args)
>   File "/usr/local/lib/python2.7/dist-packages/zc/buildout/buildout.py",
> line 666, in install
>     installed_files = self[part]._call(recipe.install)
>   File "/usr/local/lib/python2.7/dist-packages/zc/buildout/buildout.py",
> line 1410, in _call
>     return f()
>   File
> "/mailman3/mailman-bundler/eggs/collective.recipe.cmd-0.11-py2.7.egg/collective/recipe/cmd/__init__.py",
> line 56, in install
>     self.execute()
>   File
> "/mailman3/mailman-bundler/eggs/collective.recipe.cmd-0.11-py2.7.egg/collective/recipe/cmd/__init__.py",
> line 69, in execute
>     run_commands(cmds, self.shell)
>   File
> "/mailman3/mailman-bundler/eggs/collective.recipe.cmd-0.11-py2.7.egg/collective/recipe/cmd/__init__.py",
> line 39, in run_commands
>     check_call('%s %s' % (shell, tmpfile), shell=True)
>   File "/usr/lib/python2.7/subprocess.py", line 541, in check_call
>     raise CalledProcessError(retcode, cmd)
> CalledProcessError: Command 'sh /tmp/tmpez1ftK/run' returned non-zero exit
> status 127
> The command '/bin/sh -c buildout' returned a non-zero code: 1
>

Do you have any clue what happens?

Danil


On 17 July 2016 at 20:06, Simon Hanna <simon.hanna at serve-me.info> wrote:

> Hi,
>
> I started working on docker files for Mailman.
>
> I created three repositories:
> - https://github.com/simonsmiley/postorius-docker
>   Holds the files needed to create a postorius container
> - https://github.com/simonsmiley/mailman-docker
>   Holds the files needed to create a core container
> - https://github.com/simonsmiley/mailman-compose
>   Holds docker-compose files that greatly simply the process of running
>   the containers
>
> * The mailman repo currently lacks documentation
> * Currently no emails can be sent.
>   I still have to figure out what the best way is...
> * Hyperkitty will be added next
>   (together with a complete "bundler" install)
>
>
> I pushed two images to the docker hub. Their names are
> thelinuxguy/postorius and thelinuxguy/mailman
>
> I created two organizations
> mailman on docker hub and gnu-mailman on github
> https://github.com/gnu-mailman
> https://hub.docker.com/u/mailman/
>
> I know we shouldn't use github, but there is no way around
> github/bitbucket for automated builds on docker hub.
>
> I post here to inform you about the docker images and I also to ask if
> I'm allowed to keep these two organizations and move my images/repos
> there. I'll happily give push/owner access to additional people if
> requested.
>
> The repositories could be mirrored to the gitlab mailman group,
> sadly the process doesn't work the other way round just yet.
>
> In case this request gets denied, I'll just remove the organizations and
> let the images be "unofficial".
>
> cheers,
> Simon
> _______________________________________________
> Mailman-Developers mailing list
> Mailman-Developers at python.org
> https://mail.python.org/mailman/listinfo/mailman-developers
> Mailman FAQ: http://wiki.list.org/x/AgA3
> Searchable Archives: http://www.mail-archive.com/
> mailman-developers%40python.org/
> Unsubscribe: https://mail.python.org/mailman/options/mailman-
> developers/danil%40smirnov.la
>
> Security Policy: http://wiki.list.org/x/QIA9
>