Demux error when following tutorial using docker image

I am trying to use the qiime2 docker container you provide but I can’t get past the demux step. I was able to successfully import the example data from the website, and a proper .qza file was generated. But when I try to run the qiime demux step I get this error:

qiime demux emp-single --i-seqs emp-single-end-sequences.qza --m-barcodes-file sample-metadata.tsv --m-barcodes-category BarcodeSequence --o-per-sample-sequences demux.qza

Traceback (most recent call last):
File “/opt/conda/bin/qiime”, line 11, in
File “/opt/conda/lib/python3.5/site-packages/click/”, line 722, in call
return self.main(*args, **kwargs)
File “/opt/conda/lib/python3.5/site-packages/click/”, line 697, in main
rv = self.invoke(ctx)
File “/opt/conda/lib/python3.5/site-packages/click/”, line 1061, in invoke
cmd_name, cmd, args = self.resolve_command(ctx, args)
File “/opt/conda/lib/python3.5/site-packages/click/”, line 1100, in resolve_command
cmd = self.get_command(ctx, cmd_name)
File “/opt/conda/lib/python3.5/site-packages/q2cli/”, line 77, in get_command
plugin = self._plugin_lookup[name]
File “/opt/conda/lib/python3.5/site-packages/q2cli/”, line 53, in _plugin_lookup
import q2cli.cache
File “/opt/conda/lib/python3.5/site-packages/q2cli/”, line 302, in
CACHE = DeploymentCache()
File “/opt/conda/lib/python3.5/site-packages/q2cli/”, line 58, in init
self._cache_dir = self._get_cache_dir()
File “/opt/conda/lib/python3.5/site-packages/q2cli/”, line 85, in _get_cache_dir
os.makedirs(cache_dir, exist_ok=True)
File “/opt/conda/lib/python3.5/”, line 231, in makedirs
makedirs(head, mode, exist_ok)
File “/opt/conda/lib/python3.5/”, line 231, in makedirs
makedirs(head, mode, exist_ok)
File “/opt/conda/lib/python3.5/”, line 241, in makedirs
mkdir(name, mode)
PermissionError: [Errno 13] Permission denied: ‘/.config’

I’m pretty sure the issue is that qiime is trying to setup a config file at:


but I don’t have permission to write in that directory. Is there a way I can tell qiime to restrict itself to the local namespace in which I am running it?

Hi @jmartin - unfortunately this is a known issue with the official docker image (relevant issue). I don’t have an ETA for when we might address this, but thanks for letting us know. Stay tuned! Thanks :t_rex:

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.