failed to solve with frontend dockerfile.v0: failed to build LLB: failed to compute cache key: "/default.conf" not found: not found
can anyone help me with this please
I hope you named your Dockerfile as 'Dockerfile' and not something like dockerfile or DockerFile etc.
If yes please share the daemon logs.
It means that the current path where you create the docker image does not have a default.conf file, you can create a default.conf file that meets your requirements.
Related
failed to solve with frontend dockerfile.v0: failed to read dockerfile: open /var/lib/docker/tmp/buildkit-mount318724744/Dockerfile: no such file or directory
I'm just trying to build an image using sql but there is an error enter image description here
I'm unable to find a way
My Dockerfile code is:
FROM postgres:10-alphine
ADD sql/setup.sql/docker-entrypoint-initdb.d/
can anyone resolve my issue??
so I am trying to deploy my multi-docker container(Frontend, Backend, and Nginx containers) application in AWS BeansTalk. I am using CodeBuild to build the docker images using buildspec.yml file. The build fails when trying to build the first container(containerizing frontend application). Kindly refer to the image attached for the error details.
It is basically saying could not find the Dockerfile in the client directory but the funny thing is that it exists and it works as expected locally when I build the containers with docker-compose.
Here is the project directory:
buildspec.yml file:
For the benefit of others, The reason for the error is that the Dockerfile is missing in the location. Make sure you have the DockerFile inside the directory (./client in this case). It has to be exactly spelled as Dockerfile. If it's not, check the source repo and ensure that the Dockerfile file is committed.
The function ADD and COPY in my Dockerfile works remotely, but not for local files.
I tested it on a minimal setup to avoid any mistake. Is there any way to find out what is the problem?
Minimal setup
I was following the tutorial listed here to create my first blockchain network. but when I run ./startfabric.sh it gives me the error
# don't rewrite paths for Windows Git Bash users
export MSYS_NO_PATHCONV=1
docker-compose -f docker-compose.yml down
Removing network net_basic
docker-compose -f docker-compose.yml up -d ca.example.com orderer.example.com peer0.org1.example.com couchdb
Creating network "net_basic" with the default driver
Pulling couchdb (hyperledger/fabric-couchdb:latest)...
ERROR: manifest for hyperledger/fabric-couchdb:latest not found
Any help on how I could fix this?
I think you have missed the step with "Download Platform-specific Binaries", which basically takes care to download all relevant images and binary files, such that you won't have to compile them.
Please download the version of couchdb manually.
docker pull "hyperledger/fabric-couchdb:<version>"
create a tag with latest.
docker image tag hyperledger/fabric-couchdb:<version> hyperledger/fabric-couchdb:latest
NOTE:
Solution is only for this case. Why fabric-couchdb with latest tag is missing in docker hub is to be investigated.
I'm developing a web application with Play framework and I'm running it on AWS Elastic Beanstalk using a single docker container and a load balancer. Normally, everything is running fine, but when I rebuild the whole environment I get the following error:
Command failed on instance. Return code: 6 Output: (TRUNCATED)... in /etc/nginx/sites-enabled/elasticbeanstalk-nginx-docker-proxy.conf:11 nginx: [emerg] host not found in upstream "docker" in /etc/nginx/sites-enabled/elasticbeanstalk-nginx-docker-proxy.conf:24 nginx: configuration file /etc/nginx/nginx.conf test failed.
When I log into the EC2 I can see that no docker image is running and therefore the Nginx server cannot start. I cannot see any other error in the logs (or maybe I don't know where to look). The strange thing is that the same version worked fine before rebuilding the environment.
I'm using the following Dockerfile for the deployment:
FROM java
COPY <app_folder> /opt/<app_name>
WORKDIR /opt/<app_name>
CMD [ "/opt/<app_name>/bin/<app_name>", "-mem", "512", "-J-server" ]
EXPOSE 9000
Any ideas what the problem could be or where to check for more details?
I had this same problem. elasticbeanstalk-nginx-docker-proxy.conf is referring to proxy_pass http://docker but the definition of that is missing. You need to add something like
# List of application servers
upstream docker {
server 127.0.0.1:8080; # your app
}
(Make sure it's outside of the server directive.)
I have just been working through the same challenge (deploying an updated Docker image to Elastic Beanstalk). And it depends on what you want to do exactly, but what I found out is that (once you have the eb cli setup) you can just use the eb deploy command to push out your code changes without worrying about the image at all.
Granted you'd still want to push your image up to your repo for sharing purposes (with other developers), OR if you actually need to change the environment configuration for some reason... but if you're just looking to push code look into eb deploy
As far as the specifics of your error unfortunately I can't be of much help there. Good luck!