Activate enterprise version of Docker?

Product Support

AI-generated summary

L30110 upgraded Docker using the get.docker.com script and noticed a prompt to run an “activate” command to enable Docker Enterprise, but skipped it. After rebuilding the Discourse image with ./launcher rebuild app, they initially saw no change — the system still prompted for an update — until they ran the rebuild command a second time, which successfully triggered the update L30110. codinghorror clarified that the “activate” command relates to Docker’s paid Enterprise version and is not required for community users. pfaffman noted that Docker CE can be updated via apt upgrade, and L30110 confirmed they used both methods successfully and plan to rely on apt for future updates. The key takeaway is: no need to activate Docker Enterprise unless specifically required; community users can safely ignore the prompt and update via package manager.

1

Since I needed to manually rebuild the Discourse image anyway for the current upgrade, I took the opportunity to do the:

wget -qO- https://get.docker.com/ | sh

for docker upgrades as well. This appeared to go OK, but there was a note near the end of the script about doing an “activate” command to enable the Enterprise version with signature checking. I did not do this – I did not run an activate command at the end of the process. Right? Wrong?

Also, as ordered in the upgrade process for this upgrade, I just did:

cd /var/discourse
git pull
./launcher rebuild app

This began with:
Unable to find image ‘discourse/base:2.0.20190217’ locally

then a bunch of downloads and pulls, and ended with
Status: Downloaded newer image for discourse/base:2.0.20190217

However, I’ve seen no actual build and I’m still on my old Discourse image, which is still saying that update is required. I must have missed a step somewhere. Any suggestions? Thanks!

2

Turns out I needed to do:

./launcher rebuild app

a SECOND time to actually trigger the rebuild and restart. This went OK.

I’d still like to know if I should have run the “activate” command on that docker update noted above. Thanks!

3

No, that activate command has to do with upgrading to the paid enterprise version of Docker, I think.

4

If you have docker-ce then you can just update docker with

apt upgrade
5

Yeah, I actually did the docker update both ways and it appears that all is well now (Docker Engine Community version). Going forward I’ll just let apt take care of it along with all the other Ubuntu packages. Thanks.