Awesome, thank you for the information and your work. Is the GitHub URL I posted in my OP still going to be the source repo for this snap?
2 Likes
Just a thought, maybe a track might be more appropriate? Seems odd to leave a version in edge just because it is not a LTS release. 
2 Likes
I made a PR to take a stab at updating the language in the Github repo at https://github.com/docker/docker-snap/pull/43
@ijohnson @lool
At a minimum, we need to transition ownership of the docker snap package to a different launchpad organization to make it clear that Docker, Inc (“docker-inc”) is not involved. The current metadata displayed at Install docker on Linux | Snap Store is misleading. Let me know if there is anything I can do to help as an admin of “docker-inc”. I plan to archive the github repository (“docker/docker-snap”) and point users to the new effort (thanks @jcrben).
2 Likes
This is again several releases behind. Very disappointing. I understand that this is hard work (I maintain several snaps) but Docker is an important tool in the software world and this snap is Canonical trusted (or whatever the term is). The expectation would be an up-to-date snap.
I’m going to have to switch back to non-snap Docker but will check this out again in the future.
3 Likes
Is the issue here that a volunteer is needed to maintain?
1 Like
The docker snap is incredibly outdated by now. However, Ubuntu still suggest installing the snap as first option when a docker command isn’t found. Moreover, the snap is currently published by “Canonical”, which implies that it’s maintained and vetted by Canonical; which it is clearly not.
Example:
$ docker pull mariadb
Command 'docker' not found, but can be installed with:
sudo snap install docker # version 18.06.1-ce, or
sudo apt install docker.io
See 'snap info docker' for additional versions.
This snap should either be delisted or updated. Having an outdated snap for docker, a very popular app on both desktop and server, gives snaps, Canonical and Ubuntu a really bad name.
Hi, we do have an updated version of the docker snap (v18.09.3) in the edge channel, we need to wait until snapd 2.38 had been fully released before being able to completely update the docker snap, but now that it is mostly released we are testing it and will release it to stable when ready. Note that we are also still waiting on the snapd snap to be updated to 2.38 as well, as that is currently still on 2.37.4. Once the snapd snap has been updated to 2.38 we can proceed with the release as expected.
You may try it out currently with:
snap refresh docker --edge
And report back if you have any issues using it.
Thanks
1 Like
Thanks for the quick reply.
Setup instructions often contain the following additional commands to execute before using docker.
sudo addgroup --system docker
sudo adduser ubuntu docker
newgrp docker
Is this still the case with the docker snap? If so, I’d like to add these instructions to the info page of the snap. Is the source repo of the snap somewhere on Github? The original repo by docker is archived.
You can use:
assumes: snapd2.28
To ensure that only people with snapd 2.28 will get the update.
I suppose you meant assumes: snap2.38.
I am taking the opportunity to ask if all the valid assumes entries or patterns are documented anywhere.
1 Like
Yes, I’m aware of the feature, however it wasn’t clear to me what happens if we release a snap to stable that has assumes: snapd2.38 and a user is still on 2.37, when does the snap that depends on snapd 2.38 get refreshed?
As explained above at The Future of the Docker Snap the snap’s source code is on launchpad.
You do not need to create the user and group, but if you do not then you need to run docker with sudo.
I think it is “snapd” but I didn’t check. There are no other valid assumes statements, we only implemented this one AFAIR.