I'm working on a task where I need to run mongo-express to show a website. Upon running docker-compose up, I am presented with an admin error. please see the images below of both the docker-compose.yml file and a screenshot of the error. Any help would be great.
How am i able to resolve this issue.
I'm trying to run juinit on a remote postgresql docker.
I tried to use testcontainers.org but I can't get the configuration to work
I keep getting timeout exception
Does testcontainers support such setup? if so is there an example for that?
Thanks
as long as you have your Docker configured correctly, it should work out of the box without any additional configuration.
Just make sure that your environment variables point to the remote Docker daemon.
I am looking for a way to destroy a single shot container after exiting with success (0).
The docker cloud has an option called "autodestroy". Is there anything like that for Docker Swarm?
Update
I would like to autoremove a successfully exited container in a Docker Swarm by adding "special information" to the compose file.
Sorry, but no, that feature does not exist. If you were more descriptive about what you're looking to do, we might provide a better answer :)
I'm following http://bradgessler.com/articles/docker-bundler. The first time around, it made "bundler fast again". I started getting issues with some missing linked files in the gems, so I blew away the docker images, and did a docker-compose build. After it built, I could no longer do docker-compose run web bundle -- I get this:
Creating network "myapp_default" with the default driver
Pulling bundle (myapp_web:latest)...
Pulling repository docker.io/library/myapp_web
ERROR: Error: image library/myapp_web:latest not found
How do I resolve this?
Following the same article, here are the steps that worked for me:
Run docker-compose build web
Find the name of your web image: run docker images. Mine was 'appcontainer_web'
Open docker-compose.yml and replace 'image: myapp_web' with 'image: [your_image_name]'
After the above change I still encountered an error: No closing quotation. The fix was to remove the quote from "I'm" in that same docker-compose.yml file "command: echo I'm a little..."
I am new to Mongodb. When I run the following command:
sudo service mongodb start
It shows me "mongodb start/running, process 3566". But when I try to stop by giving the below command:
sudo service mongodb stop
It shows stop: Unknown instance:. Do anybody have any idea how to slove this issue.
And if I give sudo service mongodb restart, I'm getting the below message:
stop: Unknown instance:
mongodb start/running, process 3644
PS: If I'm using just mongod, I could start the server and could connect the mongo shell by giving mongo.
Please suggest me how to fix the issue and how to connect mongo shell after giving service mongodb start. Thanks in advance.
I just ran into this.
Chances are the issue is in your conf file (obviously, since you reinstalled the seeded)
In the mongodb.conf do not set fork = true if calling it as a service. This will prevent the service call from being able to access it with service mongodb.conf status/stop/restart.
Removing a fork=True line, however, will alleviate the issue.
See comments; use the other solution even though this one is accepted.
The reason you get the Unknown instance error is because upstart is tracking the wrong PID for the instance of forked mongod process. But the proper solution to this is not running the process in foreground by removing fork=true line from the config like #GoingTharn suggesting, but rather helping upstart to capture the right PID of the forked process by adding
expect daemon
to the /etc/init/mongodb.conf
I faced exactly the same problem and did the followings:
Removed the file mongod.lock (in my case this file was located at /var/lib/mongodb/)
Used the following command from my mongo client
mongo --repair
And that fixed the issue. It may be noted that I had a system crash prior to this problem appeared. Therefore, what I believe, the problem was caused due to the unclean shutdown of the server demon.
If you are unsure of the reason, you may wish to have a look at the log file (in my case I found it under /var/log/mongodb/). That might give you some useful hints.
Thanks.
I faced it as you had.Maybe it is because my computer crash unexpectedly.I use the command: sudo top(ubuntu), and I found mongo running.I killed it and start mongo.Every thing turns right.
I fixed it by myself. Below is what I did:
apt-get install mongodb
And overwrote .conf file. After that everything works fine. I hope this would help someone.