After looking further, this likely came from experimental - it's since
been pulled.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to groovy in Ubuntu.
https://bugs.launchpad.net/bugs/1460389
Title:
Version number mismatches: 2.0 beta
Groovy = 2.0 is packaged as src:groovy2 - this package will never be =
2.0.
Looks like we need an epoch (perhaps even in Debian) to unbreak this.
Triaging.
** Changed in: groovy (Ubuntu)
Status: New = Triaged
** Changed in: groovy (Ubuntu)
Importance: Undecided = Medium
--
You
127.0.0.1 inside the container isn't the same as 127.0.0.1 inside the
container.
I'm OK calling this a container misconfiguration.
I've not tried, but try setting dnsmasq to bind to the docker0 interface
(likely bind to 172.17.42.1) and hit that IP.
Otherwise you're hitting 127.0.0.1 in the
Closing as invalid. This is not required on Debian nor Ubuntu, you
likely are missing both of aufs and devicemapper, and falling back to
the lxc backend. I don't even think that relation is a recommends.
Thanks for the report, but unless this is present on Ubuntu or Debian,
it's not getting
Seems like another Mint bug. Closing.
Likely a result of command-not-found checking the wrong suite.
** Changed in: docker.io (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to docker.io in Ubuntu.
I'm marking this as Opinion.
Here's why:
The local sysadmin may have created a Docker group, but *not* intended
to give the rights to use Docker to those users. Remember, the Docker
group is root equivelent.
[tag@cassiel:~][⌚ 09:02 PM] ♥ docker run -it --rm -v /./:/mnt
debian:unstable
