Finding Docker Resources Just Got Easier 🔭
In the vast and mysterious realm of containerization, Docker users have often embarked on epic quests, akin to seeking hidden treasures. These quests, however, were less like swashbuckling adventures and more like trying to find that missing sock in your laundry – frustrating and time-consuming.
The Problem 🤦🏻
Picture this: You're a developer, DevOps guru, or an IT administrator. Your Docker environment is like a bustling metropolis, filled with containers, images, volumes, and extensions. You've just received a call that the production server is acting up, and your mission, should you choose to accept it, is to find and fix the rogue container causing chaos.
You think to yourself, "No problem, I've got this." You fire up Docker Desktop, and suddenly, you find yourself in a labyrinthine maze of menus, sub-menus, and windows. "Where on Earth is that container?" you mumble, as you navigate through an endless maze of clicks and scrolls.
The "Eureka" Moment 🎯
But behold, dear Docker user, the winds of change have blown your way. Docker Desktop introduces its latest hero: the Global Search Capability! This feature is like the treasure map you've always needed but never knew existed.
With a flourish of your keyboard and a confident click of your mouse, you invoke the Global Search. You type in the name of the container you seek, and voilà! It appears before you, like a mythical creature summoned by your Docker-wizardry.
You can't help but chuckle at the irony – all those hours spent searching for containers, and now it's as easy as finding your favorite cat meme on the internet. You might even imagine Docker Desktop whispering in your ear, "Why didn't you summon me earlier, oh seeker of containers?"
Global Search: Your Trusty Sidekick 🤝🏻
Global Search in Docker Desktop is more than just a feature; it's your trusty sidekick, your secret weapon, your ticket to a world where finding resources doesn't require a treasure map or a Sherlock Holmes hat.
This ingenious capability allows you to search for not only images and containers but also the Extensions Marketplace and Community Extensions, as well as volumes. It's like having a super-powered search engine that understands the language of Docker.
Who's This For?
- Developers
- DevOps
- IT Administrators
Global Search in Docker Desktop is a feature that can benefit anyone who works with containers and images. It can be particularly useful for developers, DevOps engineers, and IT administrators who work with complex Docker environments and need to manage multiple resources simultaneously.
In Conclusion 🔥
As you bask in the glory of finding the rogue container in record time, you realize that Docker Desktop's Global Search Capability is your trusty sidekick, your secret weapon, your ticket to a world where finding resources doesn't require a treasure map or a Sherlock Holmes hat.
So, dear Docker enthusiasts, next time you're faced with a container conundrum, remember that with Docker Desktop's Global Search, you're not just finding containers – you're finding precious moments of time, sanity, and perhaps, a good laugh along the way. Happy Docker-ing!
Getting Started 🚴🏻
Prerequisite:
- Docker Desktop 4.23.0 and above
Step 1:
Click on the “whale” icon and choose “Dashboard”.
Step 2:
Click on “Search for images,containers, volumes, extensions and more…”
Step 3:
Start typing a Docker Image name and select the Images
Start typing "Mongo," and you will see search results appearing on the screen. It shows that there are 50 images and 1 extension. I don't have a Mongo image on my local machine; this is why it's showing me the list on Hub Images.
Step 4:
Click "Run" the MongoDB container
It will start downloading this image if you are running this app for the first time
Step 5:
Configuring the settings & environment variable
You can setup environment variables like username and password as shown in the following way
Step 6:
Click "Run" the MongoDB container
Step 7:
Viewing the log
Step 8:
Accessing MogoDB Server via Mac Terminal
To achieve this, you will need to install Mongosh(Mongo Shell) software on your Mac system
brew install mongosh
Next, Run mongosh without any command-line options to connect to a MongoDB instance running on your localhost with default port 27017:
mongosh
Current Mongosh Log ID: 637857e4560a50a9c0df827c
Connecting to: mongodb://127.0.0.1:27017/?directConnection=true&serverSelectionTimeoutMS=2000&appName=mongosh+1.6.0
Using MongoDB: 6.0.3
Using Mongosh: 1.6.0
For mongosh info see: https://docs.mongodb.com/mongodb-shell/
To help improve our products, anonymous usage data is collected and sent to MongoDB periodically (https://www.mongodb.com/legal/privacy-policy).
You can opt-out by running the disableTelemetry() command.
test>
Connecting to Remote MongoDB Server
To connect to a MongoDB instance running on a remote host on port 27017 with authentication in place
mongosh "mongodb://localhost:27017" --username root -p
Enter password: ********
Current Mongosh Log ID: 6378743da440589326e2c8a2
Connecting to: mongodb://<credentials>@localhost:27017/?directConnection=true&serverSelectionTimeoutMS=2000&appName=mongosh+1.6.0
Using MongoDB: 6.0.3
Using Mongosh: 1.6.0
For mongosh info see: https://docs.mongodb.com/mongodb-shell/
------
The server generated these startup warnings when booting
2022-11-19T05:05:35.135+00:00: Using the XFS filesystem is strongly recommended with the WiredTiger storage engine. See http://dochub.mongodb.org/core/prodnotes-filesystem
2022-11-19T05:05:36.020+00:00: vm.max_map_count is too low
------
------
Enable MongoDB's free cloud-based monitoring service, which will then receive and display
metrics about your deployment (disk utilization, CPU, operation statistics, etc).
The monitoring data will be available on a MongoDB website with a unique URL accessible to you
and anyone you share the URL with. MongoDB may use this information to make product
improvements and to suggest MongoDB products and deployment options to you.
To enable free monitoring, run the following command: db.enableFreeMonitoring()
To permanently disable this reminder, run the following command: db.disableFreeMonitoring()
------
test>
Now that you've entered the MongoDB shell, you're equipped to embark on your data journey. You can begin by crafting a new collection and orchestrating an intricate symphony of CRUD operations to shape your data universe
Thanks for reading this! If you enjoyed this article, give it a virtual high-five with a 💖! If you need more info or have a burning desire for a topic I should tackle (preferably not "How to Train Your Pet Rock"), drop a comment below, and I'll try not to respond with a knock-knock joke. You can also follow me on LinkedIn, where I promise to post only the most dignified cat videos and coffee mishaps.
Top comments (0)