Closed lunloon closed 2 years ago
The docker run
command creates and starts the container.
Are you sure the container is not already created before you run the command ? You can use docker ps -a
to see existing containers.
Also, even when using the docker run
command, you still have to use docker stop
to stop the container. Won't this cause a notification?
Finally, don't forget to remove the container with docker rm
if you plan to re-create it with docker run
.
Hi thanks for the reply.
I found the error: Start container firefox failed: {"message":"Bind mount failed: '/docker/appdata/firefox' does not exists"}.
I found the solution referring to this as well https://github.com/jlesage/docker-firefox/issues/16
I forgot the root volume. Adding that in works.
Regarding docker stop
instead of docker container stop
, but as far as I have Googled, people have been saying that to stop getting notification, refer => (https://stackoverflow.com/questions/61878651/stop-synology-notification-docker-container-stopped-unexpectedly.
Anyways, docker stop firefox
works as what i wanted.
Thanks a lot for the reply.
I have set it up in Docker on my Synology NAS, and it works if i start it manually (clicking via Docker).
I am planning to run this daily on a schedule, start at a certain time and end at a certain time. I could get it working when i use "docker container start", but when i use "docker container stop" i will get a notification that the container is stopped unexpectedly.
I would like it if it does not send an email to me daily that it is stopped unexpectedly. So having found out that using "docker run" will not cause it to happen, i followed the command from the main page:
The container appears but is not started.
How can i get it to start running by itself?