I have error when working with the image?

trying to deal with Docker
that created a Dockerfile
FROM ubuntu

MAINTAINER DEVELOP DKA <hudos@rambler.ru>

RUN apt-get update && apt-get install -y cowsay && ln-s /usr/game/cowsay /usr/bin/cowsay

ENTRYPOINT ["cowsay"]


so trying to set the container
docker build-t sergalas/test-container
trying to start the container
docker run sergalas/test-container "test"
get this error message
docker: Error response from daemon: OCI runtime create failed: container_linux.go:346: starting container process caused "exec: \"cowsay\": executable file not found in $PATH": unknown.
ERRO[0001] error waiting for container: context canceled

what is the error
April 3rd 20 at 17:43
1 answer
April 3rd 20 at 17:45
Solution
See you in a folder of their project, where the Dockerfile. The command must end in a period.
docker build-t sergalas/test-container .
well, no point I would even pour failed would be a mistake
"docker build" requires exactly 1 argument. - ruben.Rogahn commented on April 3rd 20 at 17:48
Logical.
Then we go further.
First put in order doerfel
FROM ubuntu

MAINTAINER DEVELOP DKA <hudos@rambler.ru>

RUN apt-get update && apt-get install -y cowsay 

ENTRYPOINT ["/usr/games/cowsay"]


Run with argument
docker run-d --rm --name "test" sergalas/test-container aaaaa

It will be like this
5df290504fa71297114283.png - kameron commented on April 3rd 20 at 17:51
@kameron, and the symbolic link can not be directly in the Docker file to record ? - ruben.Rogahn commented on April 3rd 20 at 17:54
error is gone but the command is not executed simply
sergalas@sergalas-M68MT-D3P:/var/www/docker$ docker run-d --rm --name "test" sergalas/test-container "aaaaa"
7f7453c4bed7bffd56854549687c4a46dfcb9afb73d2e0be07b443194823920f
sergalas@sergalas-M68MT-D3P:/var/www/docker$
- ruben.Rogahn commented on April 3rd 20 at 17:57
The other mode is necessary, do not detach , a interactive
docker run -it --rm --name test sergalas/test-container "aaaaa"

detach necessary if you have in the container I had to start and leave it there hanging, what that service.. and you just took off the container in interactive mode command has executed, the container was closed and all. - kameron commented on April 3rd 20 at 18:00
Yes, everything turned out thanks. One question if you answer that is, symbolic links do not prescribe in the container ? - ruben.Rogahn commented on April 3rd 20 at 18:03
I don't even know what to answer on the merits. It seems that nothing prevents to use them if necessary.
on the other hand, I myself never experienced the need to use symlinks inside a container. - kameron commented on April 3rd 20 at 18:06
@kameron, OK, thank you very much - ruben.Rogahn commented on April 3rd 20 at 18:09
Talked with people who are more versed in the Affairs of the container, and say that symlinks normally in the Docker don't work. If you really need, then you have izgolyatsya. Overall , the use of symlinks is to avoid. Well, here's proof. https://stackoverflow.com/a/40322275 - kameron commented on April 3rd 20 at 18:12

Find more questions by tags Docker