Vaultier not applicable for docker / ubuntu / debian (Python)

Question

I am looking for a good password for my company. I wanted to test the Vaultier, but it works as expected. Neither with Docker, nor with other platforms. It is always a mistake if its Docker I get this output. I'm not a python specialist, but installing pip install --upgrade made the installation just skip the whole application.

i followed these guides https://www.vaultier.org/install/

sudo docker run -t -i --name vaultier -p 80:8088 rclick/vaultier:latest -e "VAULTIER_DOMAIN=vaultier.bla.com" Error: invalid value for -e 'VAULTIER_DOMAIN=vaultier.bla.com': bad logging level name 'VAULTIER_DOMAIN=vaultier.bla.com' For help, use /usr/bin/supervisord -h 

Running Docker without this value yields (400 Bad Request)

Using Ubuntu:

 Traceback (most recent call last): File "/opt/vaultier/venv/bin/vaultier", line 5, in <module> from pkg_resources import load_entry_point File "/opt/vaultier/venv/local/lib/python2.7/site-packages/pkg_resources.py", line 2720, in <module> parse_requirements(__requires__), Environment() File "/opt/vaultier/venv/local/lib/python2.7/site-packages/pkg_resources.py", line 592, in resolve raise VersionConflict(dist,req) # XXX put more info here pkg_resources.VersionConflict: (six 1.4.1 (/opt/vaultier/venv/lib/python2.7/site-packages), Requirement.parse('six>=1.7')) 

Using Debian:

 Traceback (most recent call last): File "/opt/vaultier/venv/local/lib/python2.7/site-packages/pip/basecommand.py", line 122, in main status = self.run(options, args) File "/opt/vaultier/venv/local/lib/python2.7/site-packages/pip/commands/install.py", line 295, in run requirement_set.install(install_options, global_options, root=options.root_path) File "/opt/vaultier/venv/local/lib/python2.7/site-packages/pip/req.py", line 1436, in install requirement.install(install_options, global_options, *args, **kwargs) File "/opt/vaultier/venv/local/lib/python2.7/site-packages/pip/req.py", line 707, in install cwd=self.source_dir, filter_stdout=self._filter_install, show_stdout=False) File "/opt/vaultier/venv/local/lib/python2.7/site-packages/pip/util.py", line 716, in call_subprocess % (command_desc, proc.returncode, cwd)) InstallationError: Command /opt/vaultier/venv/bin/python2 -c "import setuptools, tokenize;__file__='/tmp/pip-build-08foqW/psycopg2/setup.py';exec(compile(getattr(tokenize, 'open', open)(__file__).read().replace('\r\n', '\n'), __file__, 'exec'))" install --record /tmp/pip-UUDq9M-record/install-record.txt --single-version-externally-managed --compile --install-headers /opt/vaultier/venv/include/site/python2.7 failed with error code 1 in /tmp/pip-build-08foqW/psycopg2 

Any ideas on how to avoid this, or fix it?

UPDATE

after solving the "six" problem, I got a new error when running vaultier setup

  File "/opt/vaultier/venv/bin/vaultier", line 9, in <module> load_entry_point('Vaultier==0.7.5', 'console_scripts', 'vaultier')() File "/opt/vaultier/venv/local/lib/python2.7/site-packages/vaultier/vaultier/runner.py", line 231, in main settings_envvar='VAULTIER_CONF' File "/opt/vaultier/venv/local/lib/python2.7/site-packages/logan/runner.py", line 169, in run_app management.execute_from_command_line([runner_name, command] + command_args) File "/opt/vaultier/venv/local/lib/python2.7/site-packages/django/core/management/__init__.py", line 399, in execute_from_command_line utility.execute() File "/opt/vaultier/venv/local/lib/python2.7/site-packages/django/core/management/__init__.py", line 392, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/opt/vaultier/venv/local/lib/python2.7/site-packages/django/core/management/base.py", line 242, in run_from_argv self.execute(*args, **options.__dict__) File "/opt/vaultier/venv/local/lib/python2.7/site-packages/django/core/management/base.py", line 285, in execute output = self.handle(*args, **options) File "/opt/vaultier/venv/local/lib/python2.7/site-packages/vaultier/vaultier/management/commands/setup.py", line 22, in handle management.call_command('syncdb') File "/opt/vaultier/venv/local/lib/python2.7/site-packages/django/core/management/__init__.py", line 159, in call_command return klass.execute(*args, **defaults) File "/opt/vaultier/venv/local/lib/python2.7/site-packages/django/core/management/base.py", line 285, in execute output = self.handle(*args, **options) File "/opt/vaultier/venv/local/lib/python2.7/site-packages/django/core/management/base.py", line 415, in handle return self.handle_noargs(**options) File "/opt/vaultier/venv/local/lib/python2.7/site-packages/south/management/commands/syncdb.py", line 68, in handle_noargs migrations = migration.Migrations(app_label) File "/opt/vaultier/venv/local/lib/python2.7/site-packages/south/migration/base.py", line 64, in __call__ self.instances[app_label] = super(MigrationsMetaclass, self).__call__(app_label_to_app_module(app_label), **kwds) File "/opt/vaultier/venv/local/lib/python2.7/site-packages/south/migration/base.py", line 90, in __init__ self.set_application(application, force_creation, verbose_creation) File "/opt/vaultier/venv/local/lib/python2.7/site-packages/south/migration/base.py", line 154, in set_application module = importlib.import_module(self.migrations_module()) File "/opt/vaultier/venv/local/lib/python2.7/site-packages/django/utils/importlib.py", line 40, in import_module __import__(name) File "/opt/vaultier/venv/local/lib/python2.7/site-packages/kombu/transport/django/migrations/__init__.py", line 16, in <module> raise ImproperlyConfigured(SOUTH_ERROR_MESSAGE) django.core.exceptions.ImproperlyConfigured: For South support, customize the SOUTH_MIGRATION_MODULES setting to point to the correct migrations module: SOUTH_MIGRATION_MODULES = { 'kombu_transport_django': 'kombu.transport.django.south_migrations', } 

UPDATE2 -FIX

I could not find any solution on the Internet, so I tried a different version of the south and saw there ... it works. :)

  >>> DB is initialized, you can now try to run Vaultier using 'vaultier runserver' (venv) root@Vaultier :/opt/vaultier# vaultier runserver 

In the .txt requirements file from vaultier or setup.py ... it doesn't matter which one you use. just set "South == 1.0.2" Don't forget to set "Six == 1.9"

Good luck

Answer 1

I found the same problem as you, the steps I took in Ubuntu to fix it:

• Download the latest version of Vaultier: wget https://pypi.python.org/packages/source/V/Vaultier/Vaultier-0.7.5.tar.gz
• Unzip and unzip it: tar -xzvf Vaultier-0.7.5.tar.gz
• Modify the setup.py file and find the line containing six==1.4 , change six==1.9 for this,
• Install it: python setup.py install

Answer 2

If you want to use the Docker image, the current Vaultier documentation is a bit confusing.

Try the following:

• Pull the last image (don't start the image!)

  sudo docker pull rclick/vaultier:latest

• Launch Image (replace EXAMPLE.COM with the desired domain):

  sudo docker run --name vaultier -p 80:80 -e "VAULTIER_DOMAIN=EXAMPLE.COM" rclick/vaultier:latest

Answer 3

After many days of work, I learned how to install it:

If you install it using "apt-get install vaultier", then you will have a problem with the "South" and "Six" versions, so just run in parallel with "while [1]; do sed -i 's / six == 1.4 .1 / six == 1.9 / '/ tmp / pip * / setup.py; sed -i' s / South == 0.8.4 / South == 1.0.2 / '/ tmp / pip * / setup.py; done 2> / dev / null "

After successful installation, if you run "vaultier check" and you get "There is no module named vaultier.runner", set the variable PYTHON_PATH: "export PYTHONPATH =" / opt / vaultier / venv / local / lib / python 2. 7 / site-packages / vaultier "", go to / opt / vaultier / venv / bin and try again.

I'm having trouble sending emails (invite and share with others). The environment variable FROM_EMAIL or VAULTIER_FROM_EMAIL was not effective, so Vaultier used " [e-mail] " in the "from:" section of the SMTP exchange. I manually entered the desired message at the address "/opt/vaultier/venv/lib/python2.7/site-packages/vaultier/vaultier/business/mailer.py" line 33: self.from_email = ' [e-mail] '

If I have enough time, I will do OVA based on the full operation of CentOS 7.

By the way, this is a good application, it looks beautiful and works well. By the way, this is the only free you can accept. There was another, but ugly and not so easy to use.