New version avaliable of sinusbot about docker-sinusbot HOT 27 CLOSED

@RealRunSpace What version got released? The version in the image is 0.10.6-6b6bd3a.

from docker-sinusbot.

from docker-sinusbot.

@RealRunSpace You are using the galexrt/sinusbot:latest image, right?

from docker-sinusbot.

from docker-sinusbot.

@RealRunSpace I tested both images (galexrt/sinusbot:latest and quay.io/galexrt/sinusbot:latest). Both are working.
Are you sure you have repulled the images correctly with docker pull IMAGE_NAME?

from docker-sinusbot.

Used this command: docker pull quay.io/galexrt/sinusbot:latest

from docker-sinusbot.

Stop the sinusbot container, delete the sinusbot Docker image of your server and simply run the container again.

from docker-sinusbot.

how do I delete the image? (Also, I will loose any data/music?)

from docker-sinusbot.

@RealRunSpace When you are using a volume for the container in the right place, no.
The command to remove images is: docker rmi quay.io/galexrt/sinusbot:latest galexrt/sinusbot:latest

from docker-sinusbot.

ok, and now I just pull it again?

from docker-sinusbot.

I started the container and still saying this:

=> Starting SinusBot (https://sinusbot.com) by Michael Friese ...
This version has expired. Please download a newer version from the official SinusBot website and upgrade.
-> Updating sinusbot user and group id if necessary ...
-> Correcting file and mount point permissions ...
=> Corrected mount point permissions.
-> Checking if scripts directory is empty
=> Scripts directory is marked that scripts got copied. Nothing to do.
-> Checking for old data location ...
=> You are good to go! You are already using the new data directory, located at "/sinusbot/data".
=> Updating Youtube-dl...
youtube-dl is up-to-date (2017.10.07)
=> Updated youtube-dl with exit code 0
=> Starting SinusBot (https://sinusbot.com) by Michael Friese ...
This version has expired. Please download a newer version from the official SinusBot website and upgrade.```

from docker-sinusbot.

@RealRunSpace You simply run the container again. Does the same happen when you use galexrt/sinusbot:latest as the image?

from docker-sinusbot.

yep, same error in all instances

from docker-sinusbot.

@RealRunSpace What is the output of docker images for the sinusbot image?

from docker-sinusbot.

http://prntscr.com/guin20

from docker-sinusbot.

Also, I want to say that thanks for your support again :)

from docker-sinusbot.

@RealRunSpace There seems to be something wrong with the way you pull the image. The image you have is 8 weeks old. The current one is about 4 days.

In your screenshot, the image has no tag which is weird. Please post the output of docker pull galexrt/sinusbot:latest. Make sure you use galexrt/sinusbot:latest as the image and not something else.

from docker-sinusbot.

1. http://prntscr.com/guthm6
2. http://prntscr.com/guthtz
   Now I have 2, but how do I delete the one?

from docker-sinusbot.

How do I change the image without loosing data? (As I have 2 containers)
http://prntscr.com/gutiat

from docker-sinusbot.

@RealRunSpace Just replace the image name in your docker run command.
Or do you use docker-compose?

from docker-sinusbot.

I use this:
docker run --restart=always --name sinusbot8087 -d -v /opt/sinusbot/sinusbot8087:/sinusbot/data:z -p 8087:8087 galexrt/sinusbot:latest

But I don't want a new docker, just update the image of the others one, and to start them I use docker start

from docker-sinusbot.

@RealRunSpace Are you sure that you used galexrt/sinusbot:latest as the image? From the docker images screenshot you hadn't used the tag.
When you really have used -v ...:/sinusbot/data:z you can simply stop, delete and run the container with the latest image. You shouldn't lose your data because of the Docker volume mount you use.

from docker-sinusbot.

So to remove it I first kill the docker and them docker container rm sinusbot8087, and later which command do I use to create new docker containers for more instances?

from docker-sinusbot.

@RealRunSpace You stop the container, remove it with docker rm CONTAINER_ID_OR_NAME and then use your docker run command to start the container again.

I'm not going to provide any information on how to run more than one instance because that is against the license agreement of Sinusbot!

from docker-sinusbot.

oh ok!

from docker-sinusbot.

@RealRunSpace Did this solve the issue for you? If so, please close this issue thanks!
If not please let me know how can help you further.

from docker-sinusbot.

Thanks!
PD: why you don't have a [DONATE] button?

from docker-sinusbot.