Closed. This question is not reproducible or was caused by typos. It is not currently accepting answers.
This question was caused by a typo or a problem that can no longer be reproduced. While similar questions may be on-topic here, this one was resolved in a way less likely to help future readers.
Closed 6 months ago.
The community reviewed whether to reopen this question 6 months ago and left it closed:
Original close reason(s) were not resolved
Improve this question
└─# docker build -f --help
"docker build" requires exactly 1 argument.
See 'docker build --help'.
Usage: docker build [OPTIONS] PATH | URL | -
Build an image from a Dockerfile
How I can solve this error.
The solution maybe:
docker build -f <docker-file> .
You missed the ., aka the context path.
Use docker build --help and you'll get the help text for the build command, which includes help for the -f option.
Related
Closed. This question is not about programming or software development. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 3 months ago.
Improve this question
With the following image mcr.microsoft.com/cosmosdb/linux/azure-cosmos-emulator:latest when attempting to start a container either via:
Docker Desktop (Windows)
Or, via the following CLI command (Windows):
docker run --name azure-cosmosdb-emulator --memory 2GB --interactive --tty -p 8081:8081 -p 8900:8900 -p 8901:8901 -p 8902:8902 -p 10250:10250 -p 10251:10251 -p 10252:10252 -p 10253:10253 -p 10254:10254 -p 10255:10255 -p 10256:10256 -p 10350:10350 mcr.microsoft.com/cosmosdb/linux/azure-cosmos-emulator
Or, Docker Desktop (Mac)
Or, via CLI from the instructions (Mac)
https://learn.microsoft.com/en-us/azure/cosmos-db/linux-emulator?tabs=sql-api%2Cssl-netstd21#run-the-linux-emulator-on-macos
I get the same error in all the above:
2022-11-15 16:34:08 Error: The evaluation period has expired.
2022-11-15 16:34:08 ./cosmosdb-emulator: ERROR: PAL initialization failed. Error: 104
I've tried to delete the containers/image and pull latest to no avail
We are looking into this issue and update on the findings by EOD here, the new image needs to get published and it might take couple of days if everything works as expected.
as a workaround until this gets fixed, you can use the image with the tag mongodb , the same features are available
mcr.microsoft.com/cosmosdb/linux/azure-cosmos-emulator:mongodb
UPDATE:
we have published a new image , try with the latest tag
FROM mcr.microsoft.com/cosmosdb/linux/azure-cosmos-emulator:latest
There is a GitHub issue for this: https://github.com/Azure/azure-cosmos-db-emulator-docker/issues/60
At the moment it does not help to delete and pull the image. It looks like a global issue which only Microsoft can fix by pushing a new image with where the evaluation period is extended.
As a workaround you can set back the system time.
UPDATE:
It is fixed now when you pull the latest image. Lets hope we don't run into the same issue again in 178 days (13.05.2023) when the "evaluation period" expires again.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 1 year ago.
Improve this question
Checking the latest image used in the metrics-server Github repo, the tag used is v0.5.0, for arm64 I would usually add arm64 to the image name and pull it.
But the image doesn't exist and doing an inspect to the base image shows that its arch is amd64.
In google's registry the latest image is v0.3.6. So I'm not sure if support for arm64 has continued or staled.
There's no need to append arm64 starting v0.3.7, the image support multiple architectures. See official FAQ here with complete image url.
There are two tricks:
Please, check the metrics-server/README.md.
Correct registry is k8s.gcr.io
image.repository k8s.gcr.io/metrics-server/metrics-server
Seems there isn't latest tag in the registry.
So, docker run --rm k8s.gcr.io/metrics-server/metrics-server doesn't work.
But with version it works fine:
docker run --rm k8s.gcr.io/metrics-server/metrics-server:v0.5.0 --version
v.0.5.0
Closed. This question is not reproducible or was caused by typos. It is not currently accepting answers.
This question was caused by a typo or a problem that can no longer be reproduced. While similar questions may be on-topic here, this one was resolved in a way less likely to help future readers.
Closed 1 year ago.
Improve this question
I am trying to use a base image for docker using Ubuntu 20.04 and Cuda 11.2 (as it is on my machine) to be used with tensorflow 2.5.
I modified a previous version of Ubuntu 18.04 I had. This dockerfile works fine:
FROM nvidia/cuda:10.0-runtime-ubuntu18.04
CMD nvidia-smi
but this one does not (which is a direct transcription of the previous one):
FROM nvidia/cuda:11.2-runtime-ubuntu20.04
CMD nvidia-smi
manifest for nvidia/cuda:11.2-runtime-ubuntu20.04 not found: manifest
unknown: manifest unknown
neither do this:
FROM nvidia/11.2.0-runtime-ubuntu18.04
CMD nvidia-smi
pull access denied for nvidia/11.2.0-runtime-ubuntu18.04, repository
does not exist or may require 'docker login': denied: requested access
to the resource is denied
I concluded that this is the case here: there is no relevant image to the docker server since the message is misleading. But in the documentation is appears valid.
The same is true about this one:
FROM nvidia/11.2.0-runtime-ubuntu20.04
CMD nvidia-smi
So, can someone provide some advice over how can I use a cuda 11.2+Ubuntu 20.04 image?
Basically all of the examples except the first one are referring to non-existent images.
Here is a wrong version number:
FROM nvidia/cuda:11.2-runtime-ubuntu20.04
Here you've lost image name (cuda):
FROM nvidia/11.2.0-runtime-ubuntu18.04
Should be cuda:11.2.0-...:
FROM nvidia/cuda:11.2.0-runtime-ubuntu20.04
The list of available versions is available at Docker Hub. Also, instead of using Dockerfile, you can check if an image exists with this short command:
sudo docker run --rm --gpus all nvidia/cuda:11.2.0-runtime-ubuntu20.04 nvidia-smi
The image you are looking for is available here.
You have missed to add the proper image name. It should be nvidia/cuda:11.2.0-runtime-ubuntu20.04. You have missed the cuda: part.
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 8 years ago.
Improve this question
What does this command actually do in jenkins build?
Windows Batch Command:
start bash ./startTomcat.sh
I see many xml files in tomcat folder after the build is over and the build fails....
There are multiple issues here:
You are not supposed to start tomcat from within a Jenkins-job
(see also here Process leaked file descriptors error on JENKINS).
Tomcat is started as a unix command, while you try to run it from a Windows command - this will never work.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I installed Jenkins yesterday (together with apache2). Jenkins started fine and everything was ok. Then I decided to stop jenkins and apache because I planned to configure them today. Now when I start Jenkins i get this error:
Jenkins startup error
I have tried some other Ports like 8081 or 4xxxx, nothing helped.
How can i fix this? Please help.
System:
Debian 6.0
Installation of Jenkins through the offical repo.
Apache has no vhosts except the 000-default
netstat shows nothing on 8080 or the 4xxxx Port
The problem is quite easy to pin:
Caused by: java.net.BindException: Address already in use
This means that for the given address:port there is already a process which is binding to it. Please, use the operating system tools to find this process and, eventually, kill it. Then start Jenkins again.
Additionally, I can add, that it almost certainly Jenkins, which was not stopped correctly or, due to some error, did not stopped entirely.