squid-deb-proxy vs lxd bridge
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| lxd (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
| squid-deb-proxy (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
With the old lxc network bridge, it was always up so squid-deb-proxy could bind to the bridges IP address and be available to lxc containers. The new bridge with lxd is unstable however, and brought up and down as required. I no longer have any fixed IP addresses accessible to my lxd containers that squid-deb-proxy can be bound to.
Would it be possible to have squid-deb-proxy restarted whenever the lxd bridge is brought up, allowing the old behaviour to work? Or for the lxd bridge to be pinned somehow, so it remains bound even when all the lxd containers are shut down?
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: squid-deb-proxy 0.8.14
ProcVersionSign
Uname: Linux 4.4.0-21-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Apr 21 16:09:35 2016
InstallationDate: Installed on 2016-02-26 (54 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224)
PackageArchitec
SourcePackage: squid-deb-proxy
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile.
mtime.conffile.
mtime.conffile.
upstart.
| Stuart Bishop (stub) wrote | #1 |
| Stuart Bishop (stub) wrote | #2 |
| Stéphane Graber (stgraber) wrote | #3 |
| Changed in lxd (Ubuntu): | |
| status: | New → Invalid |
Adding lxd for input, as a common use case is for containers to be configured to use a local cache and this cache needs to be available when the containers are started up.