remove docker (ubuntu) in presence of docker-ce
![Creative The name of the picture](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgO9GURib1T8z7lCwjOGLQaGtrueEthgQ8LO42ZX8cOfTqDK4jvDDpKkLFwf2J49kYCMNW7d4ABih_XCb_2UXdq5fPJDkoyg7-8g_YfRUot-XnaXkNYycsNp7lA5_TW9td0FFpLQ2APzKcZ/s1600/1.jpg)
![Creative The name of the picture](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhYQ0N5W1qAOxLP7t7iOM6O6AzbZnkXUy16s7P_CWfOb5UbTQY_aDsc727chyphenhyphen5W4IppVNernMMQeaUFTB_rFzAd95_CDt-tnwN-nBx6JyUp2duGjPaL5-VgNO41AVsA_vu30EJcipdDG409/s400/Clash+Royale+CLAN+TAG%2523URR8PPP.png)
up vote
0
down vote
favorite
I have docker
up and running, with the docker-provided CE variant:
# dpkg -l '*docker*'
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-===================================================-==============================-==============================-===========================================================================================================
un docker <none> <none> (no description available)
ii docker-ce 18.03.0~ce-0~ubuntu amd64 Docker: the open-source application container engine
un docker-ee <none> <none> (no description available)
rc docker-engine 17.05.0~ce-0~ubuntu-xenial amd64 Docker: the open-source application container engine
un docker-engine-cs <none> <none> (no description available)
un docker.io <none> <none> (no description available)
I'm doing basic system house-keeping and see that the older docker-engine
has some config files still present. I thought to do a simple apt-get purge docker-engine
, but thought I'd look into what would happen. The /var/lib/dpkg/info/docker-engine.list
just contains:
/etc
/etc/init.d
/etc/default
/etc/init
so I'm not worried that purging would harm the current docker-ce
package, but the .postrm
file does a bit more. In if
blocks specifically limited to "purge"
operations, I see:
update-rc.d docker remove >/dev/null
deb-systemd-helper purge docker.service docker.socket >/dev/null
deb-systemd-helper unmask docker.service docker.socket >/dev/null
which do not (to me) immediately differentiate between the two packages. The first command looks for /etc/init.d/docker
which, at this point, is the one installed by docker-ce
, so I wonder if executing that command would close down the wrong service.
I can recover from a simple "service was disabled", but I don't know what else will be happening to know if apt-get purge docker-engine
would further disrupt my current happily-working docker-ce
instance.
If my concern is correct (that purging one will adversely affect the other), then is there a safer way to clean this up? I do not mind removing files manually, if that will suffice. My sole goal is to not endanger my current docker instance, as it feeds my company's docker swarm
manager, on which I have a lot riding.
16.04 apt package-management dpkg
add a comment |Â
up vote
0
down vote
favorite
I have docker
up and running, with the docker-provided CE variant:
# dpkg -l '*docker*'
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-===================================================-==============================-==============================-===========================================================================================================
un docker <none> <none> (no description available)
ii docker-ce 18.03.0~ce-0~ubuntu amd64 Docker: the open-source application container engine
un docker-ee <none> <none> (no description available)
rc docker-engine 17.05.0~ce-0~ubuntu-xenial amd64 Docker: the open-source application container engine
un docker-engine-cs <none> <none> (no description available)
un docker.io <none> <none> (no description available)
I'm doing basic system house-keeping and see that the older docker-engine
has some config files still present. I thought to do a simple apt-get purge docker-engine
, but thought I'd look into what would happen. The /var/lib/dpkg/info/docker-engine.list
just contains:
/etc
/etc/init.d
/etc/default
/etc/init
so I'm not worried that purging would harm the current docker-ce
package, but the .postrm
file does a bit more. In if
blocks specifically limited to "purge"
operations, I see:
update-rc.d docker remove >/dev/null
deb-systemd-helper purge docker.service docker.socket >/dev/null
deb-systemd-helper unmask docker.service docker.socket >/dev/null
which do not (to me) immediately differentiate between the two packages. The first command looks for /etc/init.d/docker
which, at this point, is the one installed by docker-ce
, so I wonder if executing that command would close down the wrong service.
I can recover from a simple "service was disabled", but I don't know what else will be happening to know if apt-get purge docker-engine
would further disrupt my current happily-working docker-ce
instance.
If my concern is correct (that purging one will adversely affect the other), then is there a safer way to clean this up? I do not mind removing files manually, if that will suffice. My sole goal is to not endanger my current docker instance, as it feeds my company's docker swarm
manager, on which I have a lot riding.
16.04 apt package-management dpkg
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have docker
up and running, with the docker-provided CE variant:
# dpkg -l '*docker*'
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-===================================================-==============================-==============================-===========================================================================================================
un docker <none> <none> (no description available)
ii docker-ce 18.03.0~ce-0~ubuntu amd64 Docker: the open-source application container engine
un docker-ee <none> <none> (no description available)
rc docker-engine 17.05.0~ce-0~ubuntu-xenial amd64 Docker: the open-source application container engine
un docker-engine-cs <none> <none> (no description available)
un docker.io <none> <none> (no description available)
I'm doing basic system house-keeping and see that the older docker-engine
has some config files still present. I thought to do a simple apt-get purge docker-engine
, but thought I'd look into what would happen. The /var/lib/dpkg/info/docker-engine.list
just contains:
/etc
/etc/init.d
/etc/default
/etc/init
so I'm not worried that purging would harm the current docker-ce
package, but the .postrm
file does a bit more. In if
blocks specifically limited to "purge"
operations, I see:
update-rc.d docker remove >/dev/null
deb-systemd-helper purge docker.service docker.socket >/dev/null
deb-systemd-helper unmask docker.service docker.socket >/dev/null
which do not (to me) immediately differentiate between the two packages. The first command looks for /etc/init.d/docker
which, at this point, is the one installed by docker-ce
, so I wonder if executing that command would close down the wrong service.
I can recover from a simple "service was disabled", but I don't know what else will be happening to know if apt-get purge docker-engine
would further disrupt my current happily-working docker-ce
instance.
If my concern is correct (that purging one will adversely affect the other), then is there a safer way to clean this up? I do not mind removing files manually, if that will suffice. My sole goal is to not endanger my current docker instance, as it feeds my company's docker swarm
manager, on which I have a lot riding.
16.04 apt package-management dpkg
I have docker
up and running, with the docker-provided CE variant:
# dpkg -l '*docker*'
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-===================================================-==============================-==============================-===========================================================================================================
un docker <none> <none> (no description available)
ii docker-ce 18.03.0~ce-0~ubuntu amd64 Docker: the open-source application container engine
un docker-ee <none> <none> (no description available)
rc docker-engine 17.05.0~ce-0~ubuntu-xenial amd64 Docker: the open-source application container engine
un docker-engine-cs <none> <none> (no description available)
un docker.io <none> <none> (no description available)
I'm doing basic system house-keeping and see that the older docker-engine
has some config files still present. I thought to do a simple apt-get purge docker-engine
, but thought I'd look into what would happen. The /var/lib/dpkg/info/docker-engine.list
just contains:
/etc
/etc/init.d
/etc/default
/etc/init
so I'm not worried that purging would harm the current docker-ce
package, but the .postrm
file does a bit more. In if
blocks specifically limited to "purge"
operations, I see:
update-rc.d docker remove >/dev/null
deb-systemd-helper purge docker.service docker.socket >/dev/null
deb-systemd-helper unmask docker.service docker.socket >/dev/null
which do not (to me) immediately differentiate between the two packages. The first command looks for /etc/init.d/docker
which, at this point, is the one installed by docker-ce
, so I wonder if executing that command would close down the wrong service.
I can recover from a simple "service was disabled", but I don't know what else will be happening to know if apt-get purge docker-engine
would further disrupt my current happily-working docker-ce
instance.
If my concern is correct (that purging one will adversely affect the other), then is there a safer way to clean this up? I do not mind removing files manually, if that will suffice. My sole goal is to not endanger my current docker instance, as it feeds my company's docker swarm
manager, on which I have a lot riding.
16.04 apt package-management dpkg
asked Apr 23 at 19:00
![](https://i.stack.imgur.com/gteVQ.jpg?s=32&g=1)
![](https://i.stack.imgur.com/gteVQ.jpg?s=32&g=1)
r2evans
1215
1215
add a comment |Â
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1027563%2fremove-docker-ubuntu-in-presence-of-docker-ce%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password