# How to access the Solace CLI

**URL:** <https://community.solace.com/t/how-to-access-the-solace-cli/1190>\
**Category:** Solace Event Broker\
**Tags:** cli\
**Created:** [March 18, 2022, 4:44am UTC](https://community.solace.com/t/how-to-access-the-solace-cli/1190 "2022-03-18T04:44:10Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![sulfred](https://yyz1.discourse-cdn.com/solace/user_avatar/community.solace.com/sulfred/32/48_2.png) [@sulfred](https://community.solace.com/u/sulfred)\
**Post date:** [March 18, 2022, 4:44am UTC](https://community.solace.com/t/how-to-access-the-solace-cli/1190/1 "2022-03-18T04:44:10Z")

</div>

I am using docker image to run the solace broker. The image is solace/solace-pubsub-standard:latest . I would like to access the CLI and for example check the current version or log checking.  
I followed the steps but it seems that there is not enough access right for me. I would like to ask what is the correct way to access the CLI in a docker container.

Thanks,

I am referencing to these doc:  
[Default Configuration for Software Event Brokers](https://docs.solace.com/Configuring-and-Managing/SW-Broker-Specific-Config/Access-Solace-CLI.htm)[Default Configuration for Software Event Brokers](https://docs.solace.com/Configuring-and-Managing/SW-Broker-Specific-Config/Cloud-And-Machine-Tasks/Displaying-Versions.htm)[Displaying and Clearing Logs](https://docs.solace.com/Configuring-and-Managing/Displaying-Logs.htm) \> # I think I can access as anonymous mode

> docker exec -it solace /usr/sw/loads/currentload/bin/cli -A  
> Solace PubSub+ Standard Version 9.12.1.17  
> The Solace PubSub+ Standard is proprietary software of  
> Solace Corporation. By accessing the Solace PubSub+ Standard  
> you are agreeing to the license terms and conditions located at  
> [http://www.solace.com/license-software](http://www.solace.com/license-software)  
> Copyright 2004-2021 Solace Corporation. All rights reserved.  
> To purchase product support, please contact Solace at:  
> [https://solace.com/contact-us/](https://solace.com/contact-us/)  
> Operating Mode: Message Routing Node  
> 0f723cecbb20\> solacectl version  
> &nbsp;Invalid command input  
> &nbsp; &nbsp; &nbsp; &nbsp; solacectl version  
> &nbsp; &nbsp; &nbsp; &nbsp; ^  
> &nbsp; &nbsp; &nbsp; &nbsp; → unknown command, or command not available in current mode

---

<div class="post-metadata">

**Author:** ![uherbst](https://yyz1.discourse-cdn.com/solace/user_avatar/community.solace.com/uherbst/32/291_2.png) [@uherbst](https://community.solace.com/u/uherbst)\
**Post date:** [March 18, 2022, 6:27am UTC](https://community.solace.com/t/how-to-access-the-solace-cli/1190/2 "2022-03-18T06:27:06Z")

</div>

Hi @sulfred ,

> your way of access cli is absolutely fine.  
> If you access cli this way, you have global admin permission.  
> Only with your command in cli, you’re not correct.  
> Just type  
> show version  
> This gives you all the version information.  
> The complete reference for cli commands can be found here:  
> [CLI Command Reference](https://docs.solace.com/Solace-CLI/CLI-Reference/Command-Line-Reference.htm)  
> Have a nice day.  
> Uli

---

<div class="post-metadata">

**Author:** ![sulfred](https://yyz1.discourse-cdn.com/solace/user_avatar/community.solace.com/sulfred/32/48_2.png) [@sulfred](https://community.solace.com/u/sulfred)\
**Post date:** [March 18, 2022, 6:42am UTC](https://community.solace.com/t/how-to-access-the-solace-cli/1190/3 "2022-03-18T06:42:20Z")

</div>

Thanks for the reply, that works.

---

<div class="post-metadata">

**Author:** ![Tamimi](https://yyz1.discourse-cdn.com/solace/user_avatar/community.solace.com/tamimi/32/2190_2.png) [@Tamimi](https://community.solace.com/u/Tamimi)\
**Post date:** [March 18, 2022, 2:49pm UTC](https://community.solace.com/t/how-to-access-the-solace-cli/1190/4 "2022-03-18T14:49:09Z")

</div>

A quick tip on this that @Aaron \> pointed out to me a while back, you can access to Solace CLI in shorter form like this  
docker exec -it solace cli

---

<div class="post-metadata">

**Author:** ![Aaron](https://yyz1.discourse-cdn.com/solace/user_avatar/community.solace.com/aaron/32/843_2.png) [@Aaron](https://community.solace.com/u/Aaron)\
**Post date:** [March 22, 2022, 2:45am UTC](https://community.solace.com/t/how-to-access-the-solace-cli/1190/5 "2022-03-22T02:45:08Z")

</div>

Yup! You can also ssh \> into the Docker container, if it was running on a different host (or just use localhost):  
ssh -p 2222 admin@  
@sulfred the “solacectl” commands are for when you’re using a machine image (like VirtualBox or VMWare), not Docker.  
p.s. I love CLI, and still use it more than the PubSub+Manager GUI…! ?

---

<div class="post-metadata">

**Author:** ![sulfred](https://yyz1.discourse-cdn.com/solace/user_avatar/community.solace.com/sulfred/32/48_2.png) [@sulfred](https://community.solace.com/u/sulfred)\
**Post date:** [March 22, 2022, 3:35am UTC](https://community.solace.com/t/how-to-access-the-solace-cli/1190/6 "2022-03-22T03:35:53Z")

</div>

> [@Aaron](#):
>
> Yup! You can also ssh \> into the Docker container, if it was running on a different host (or just use localhost):  
> ssh -p 2222 admin@  
> @sulfred the “solacectl” commands are for when you’re using a machine image (like VirtualBox or VMWare), not Docker.  
> p.s. I love CLI, and still use it more than the PubSub+Manager GUI…! ?

Thanks @Aaron for your information. As a beginner, I will stick into the GUI first but I cam imagine how fast if one is familiar with the CLI. lol
