How do I manually update Discourse and Docker image to latest?


(R3trosteve) #87

I may be being impatient, but I seem to have become stuck at this point in the process:

The site has not come online and scrolling through the stack trace I don’t see any errors of note.

It’s been like this for 23 minutes so far… any clues?


(Jeff Atwood) #88

Are you out of disk space? Out of memory? log in with another SSH console and check:

free -m
df -m


#89

Same thing here, mines stuck upgrading.

root@hn:~# free -m
             total       used       free     shared    buffers     cached
Mem:           994        653        340         23         85        385
-/+ buffers/cache:        182        811
Swap:         2047        105       1942


root@hn:~# df -m
Filesystem                1M-blocks  Used Available Use% Mounted on
udev                            487     1       487   1% /dev
tmpfs                           100     1       100   1% /run
/dev/disk/by-label/DOROOT     30110  8338     20221  30% /
none                              1     0         1   0% /sys/fs/cgroup
none                              5     0         5   0% /run/lock
none                            498     1       497   1% /run/shm
none                            100     0       100   0% /run/user
none                          30110  8338     20221  30% /var/lib/docker/aufs/mnt/a0d0f602e8cff892704185107622c5cb14da7f39142f277f43c5176446442082

(R3trosteve) #90
root@community:/var/discourse# free -m
             total       used       free     shared    buffers     cached
Mem:           994        623        370          0         88        357
-/+ buffers/cache:        177        816
Swap:         2047         51       1996
root@community:/var/discourse# df -m
Filesystem     1M-blocks  Used Available Use% Mounted on
/dev/vda1          30108 20175      8382  71% /
none                   1     0         1   0% /sys/fs/cgroup
udev                 487     1       487   1% /dev
tmpfs                100     1       100   1% /run
none                   5     0         5   0% /run/lock
none                 498     1       497   1% /run/shm
none                 100     0       100   0% /run

(R3trosteve) #91

OK, so, if in doubt do all the spring cleaning stuff first…

Happy to report back up and running. Thanks!


#92

Up and running again, it was a bug in the launcher script. https://github.com/discourse/discourse_docker/commit/3a8ad47b6e5908a3fcb6e069915ccd3ea0b7e4a4


(Himanshu Chhangani) #93

Hi,

I have installed discourse setup on centos 6.6 !
now problem is I cant update docker itself, hence stuck with loop, update docker first then discourse…!
can I downgrade ??

OS updating is pain, as its a EC2 instance…!


#94

Hi @sam,

I am facing the same problem as @jehrlich. I followed the command you posted but I continue to get “E: Unable to locate package docker-engine”. I am not sure how to solve it since I am not trained as a programmer. I was wondering if you could give more detailed instruction? I love Discourse and would really appreciate the help to get my forum up and running again! Thank you!


#95

Okay, I don’t have to update discourse. But I have attached to the existing container and did an OS update, such as apt-get update/upgrade. There were a lot of updates. I then committed the container updates back to a new image. I tagged the new image with the latest release that I have. ie. discourse/discourse:1.7.0.

So, now I have the original image and the updated image. How do I tell the launcher to use the image by its tag? Or will it do it automatically base on the tag being higher. I do not have a latest tag.

Just as an FYI, the size of the new image was nearly double the size of the old (5 months difference).

Thanks in Advance.


(Sam Saffron) #96

Launcher automatically hardcodes the tag name of latest supported image. If you wish to override use:

base_image: whatever/image:1.0

#97

Thanks for the fast reply.

Where is that set exactly? On the command line or somewhere else?


(Sam Saffron) #98

In the yaml file in /var/docker/containers/app.yml


#99

Perfect! Thanks again. Given that it is in the app.yml file, any updates to discourse will not be affected by this as this is what was setup from the beginning or has been updated since.


(Veer) #100

Thanks , i upgraded after upgrading the dockker.


(Dylan Hunt) #101

This is still the #1 search thread, but it’s outdated.


(Lutz Biermann) #102

If you use Ubuntu, its “docker.io”.

dpkg -l docker.io
ii  docker.io                1.12.3-0ubuntu4~1 amd64             Linux container runtime

(Lee_Ars) #103

The docker-engine package is maintained by the Docker folks and will always be more up to date. Unless you have a specific reason to use docker.io, you’re better off with docker-engine.

(The auto-install script at get.docker.com will add the correct PPA for docker-engine and also download the needed dependencies. Once run, apt update and apt upgrade will keep it up to date.)


(Jay Pfaffman) #104

I already :heart:ed this post, but I still want to say thanks for explaining this so clearly, especially the final parenthetical, which is the real gem of this post.


#105

Does using cleanup require current session to be turned off?


(Andrew Waugh) #106

No, all cleanup does is remove the docker images which are no longer in use - it doesn’t affect the running site.

n.b. if you are only running discourse on the box then cleanup is 100% safe, but if you have other docker images installed it may cause problems.