I am working on deploying a Joomla application on a Linux server using Docker. When I use the docker-compose start command, I get the following error:
Error
"Cannot start service joomla-1: get 7bc8fef95dc63f2c845e57c3b5be68cb872179c02b0db8eeed5468e57cce1484: no such volume"
I have checked the images are available.
This was working properly before, but suddenly stopped working. Can anyone help me on this?
There is something wrong with the container Volume. Try to delete your container first and then create it again.
docker container prune
and then
docker-compose up
Related
I've been folowing the tutorial but I cant create the mysql container. I have already tryed to remove the network and make it all over again and still not working.
It says it has files in the directory "/var/lib/mysql/" but I dont have that directory.
I have tryed to create and run a container and expected a runing container
After my server rebooted, docker containers are still present in /var/lib/docker/containers but don't appear in docker ps -a and cannot be started by ID. Essentially, the data seems to exist but docker doesn't know it's there and/or doesn't know how to start it. For the record, the server is running Alpine Linux.
I tried calling docker start directly with the ID of a container and this was the output:
hostname:~# docker start 1d896bb6aa3b224fbfcaae92ad309bd99de5115fd557195ba309d760e729eac6/
Error response from daemon: No such container: 1d896bb6aa3b224fbfcaae92ad309bd99de5115fd557195ba309d760e729eac6
Error: failed to start containers: 1d896bb6aa3b224fbfcaae92ad309bd99de5115fd557195ba309d760e729eac6/
I've also tried creating new containers to see if they can be used and new containers seem to work fine, just the old ones are messed up.
So I got to know about Azure and I want to run a nodejs file in VM. I know the steps on how to deploy the nodejs in Digital Ocean, and It worked fine. I tried to follow the same steps but seems like there were some issues while pulling images from docker.
I followed this tutorial in order to install docker in my VM. But it seems like there is an issue:
Error response from daemon: Get "https://registry-1.docker.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
on running sudo docker pull hello-world
while the same error is occuring on docker-compose
(This is just an example, I want to run docker-compose but It gave the same error)
I tried running all the solutions that I found but all didn't help. Is there anyone else who has created a vm in azure and came across this issue and fixed it?
I found about 5-6 links with the same question but none of the answers fixed my problem :(
I created a Linux VM with the help of this tutorial
Look for the image on hub.docker.com and make sure that you pass a correct name of the image. The article is from 2018 so it could be out dated.
I tried installing docker on a server of mine using this tutorial.
I want to run docker images remotely and use the portainer web-interface to administrate everything.
However, when I get to the point where I need to test my installation and I enter the command $ sudo docker run hello-world, I only get the following error:
docker: Error response from daemon: OCI runtime create failed: container_linux.go:344: starting container process caused "process_linux.go:424: container init caused \"join session keyring: create session key: disk quota exceeded\"": unknown. ERRO[0000] error waiting for container: context canceled
I tried the following methods:
"Install Docker CE / Install using the convenience script"
"Install Docker CE / Install using the repository"
This also happens when I try to run other images (eg. portainer).
I hope this is enough information.
I am new to docker, so I don't know how I should debug it efficiently.
Try to increase maxkeys kernel parameter:
echo 50000 > /proc/sys/kernel/keys/maxkeys
see: https://discuss.linuxcontainers.org/t/error-with-docker-inside-lxc-container/922/2
So, as it turns out, I connected to the wrong vServer.
The one I was connected to is using LXD (as you might have seen in my previous comment), which doesn't support Docker (at least not the way this guide advises).
When I ran the same setup on a vServer using a bare-metal(type 1) hypervisor, it worked without a problem.
I think this has to do with automatic storage allocation under LXD, but this is just a guess.
I am getting following error when i am trying to push my application to Openshift server. I have updated only package.json and trying to upload it on server then it showing this error.
So i have written couple of command to find out this error. So i found the following error but i am not getting what should i do now to fix this error.
My package.json is following below. If you think that there is some error in this package.json, please inform me. It is running fine on localhost but i do not know it is not able to find out package.json.
it's possible that the existing running application is not getting stopped correctly. Try using the rhc app stop command to completely stop your application, and then ssh to your gear (rhc ssh) and use the "ps -ef" command to make sure nothing else is running that would be taking up that port.