Adding authentication variable to container

[vonfrank]

Hi there

 

I am creating a docker manually in the wizard on my unraid system. I use a docker hub repository, in my case the original docker container for mongodb. I want to add the authentication variable ( --auth) to my run command, but i can't figure out where to put it. The original string for running the command is "$ docker run --name some-mongo -d mongo --auth"

 

I have managed to make it work, by putting the --auth variable behind the repository field, but i have to delete it every time i update my container, and my icon doesn't work. Isn't there a more "right" way to add this variable?

 

This is my custom template so far. Thanks!

[saarg]

If --auth is a variable you simply click where it says  Add another Path, Port or Variable and choose variable and add the info.

[vonfrank]

If --auth is a variable you simply click where it says  Add another Path, Port or Variable and choose variable and add the info.

 

hmm.. I don't know if it is a variable or if it just is my word for it. How do i see this? It's this docker, and the authentication part is defined about 40% down the page.. Thanks.. https://hub.docker.com/_/mongo/

[CHBMB]

Put it in the extra parameters box and see if that boxes.

 

Sent from my C6903 using Tapatalk

 

 

[vonfrank]

Put it in the extra parameters box and see if that boxes.

 

Sent from my C6903 using Tapatalk

 

Hmm.. I tried this, and got a little further.. I tried " --auth" and "-d mongo --auth". The last one made it able to complete, but not start. But i saw a pattern. If i put it behind the repository field, (here it works, but can't update, and other small errors), the --auth comes behind the mongo command. If i put them in the extra parameters field, it goes in front of the mongo command.

 

I need the --auth to be the last part of the command. Any ideas?

[CHBMB]

Put it in the extra parameters box and see if that boxes.

 

Sent from my C6903 using Tapatalk

 

Hmm.. I tried this, and got a little further.. I tried " --auth" and "-d mongo --auth". The last one made it able to complete, but not start. But i saw a pattern. If i put it behind the repository field, (here it works, but can't update, and other small errors), the --auth comes behind the mongo command. If i put them in the extra parameters field, it goes in front of the mongo command.

 

I need the --auth to be the last part of the command. Any ideas?

 

Just playing around with this out of curiosity, looking at the readme there's nothing about --auth, where are you getting that from?

[saarg]

--auth is a command line argument for mongod, so the only way to make this work for unraid is to put it in the repo box.

[vonfrank]

Put it in the extra parameters box and see if that boxes.

 

Sent from my C6903 using Tapatalk

 

Hmm.. I tried this, and got a little further.. I tried " --auth" and "-d mongo --auth". The last one made it able to complete, but not start. But i saw a pattern. If i put it behind the repository field, (here it works, but can't update, and other small errors), the --auth comes behind the mongo command. If i put them in the extra parameters field, it goes in front of the mongo command.

 

I need the --auth to be the last part of the command. Any ideas?

 

Just playing around with this out of curiosity, looking at the readme there's nothing about --auth, where are you getting that from?

 

Im not an expert, but from the docker hub page.. Around 40% down.. https://hub.docker.com/_/mongo/ there is a section of authentication.

[vonfrank]

--auth is a command line argument for mongod, so the only way to make this work for unraid is to put it in the repo box.

 

what a shame.. does this mean the repo box is actually a placing its input in the commandline argument field of a docker command? If you understand..

[vonfrank]

whenever i try to update.. it tries to update from mongo --auth:latest and not mongo:latest.....

[saarg]

whenever i try to update.. it tries to update from mongo --auth:latest and not mongo:latest.....

 

Everything you add in the template ends up in the run command.

 

Every time you want to update the container you will need to remove --auth.

[vonfrank]

whenever i try to update.. it tries to update from mongo --auth:latest and not mongo:latest.....

 

Everything you add in the template ends up in the run command.

 

Every time you want to update the container you will need to remove --auth.

 

Okay, thank you! Do you know if there is another workaround?

[CHBMB]

whenever i try to update.. it tries to update from mongo --auth:latest and not mongo:latest.....

 

Everything you add in the template ends up in the run command.

 

Every time you want to update the container you will need to remove --auth.

 

That is the workaround....

 

Okay, thank you! Do you know if there is another workaround?

[FreakyBigFoot]

Did you ever figure this out? I'm running into the same issue currently.