mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #347] dnsmasq doesn't start #246
Labels
No labels
LTS merge
LTS merge
bug
bug
converted-to-discussion
doc-todo
documentation
duplicate
enhancement
file-transfer
firecfg
firejail-in-firejail
firetools
graphics
help wanted
information_old
installation
invalid
modif
moved
needinfo
networking
notabug
notourbug
old-version
overlayfs
packaging
profile-request
pull-request
question
question_old
removal
runtime-permissions
sandbox-ipc
security
stale
wiki
wiki
wontfix
wordpress
workaround
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/firejail#246
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @curiosity-seeker on GitHub (Mar 3, 2016).
Original GitHub issue: https://github.com/netblue30/firejail/issues/347
I've created the following profile for dnsmasq:
After booting my computer dnsmasq is not active. systemctl status dnsmasq says:
However, after executing
sudo systemctl restart dnsmasqall is well! What could be the reason? What does the error above mean?Note that I'm using firejail 0.9.39, but the problem also occurred with v. 0.9.38.
@netblue30 commented on GitHub (Mar 4, 2016):
Does it happen every time you start the computer?
@curiosity-seeker commented on GitHub (Mar 4, 2016):
Yes, it happens always. I also tried to solve the problem by adding an After=dnscrypt-proxy.service entry to the [Unit] section in override.conf to make sure that dnsmasq starts after dnscrypt-proxy - but to no avail.
@netblue30 commented on GitHub (Mar 5, 2016):
Firejail needs some directories under /run, such as /run/firejail/mnt, /run/firejail/name etc. If the directories are not there, firejail will try to create them - it has root privileges when it does it. The only way this fails is /run was not mounted. At least on my Debian Jessie box I have /run mounted at startup by systemd as a temporary filesystem. I guess you have to start firejail after /run was mounted.
@curiosity-seeker commented on GitHub (Mar 6, 2016):
Hm, but the thing is that two firejailed instances of dnscrypt-proxy (using different DNS resolvers) are also started without problems. So it seems that the /run mount is not the culprit.
I should also add that I had used a firejailed dnsmasq until some months ago before I temporarily switched to unbound. It hadn't caused problems then but it does now. So something has changed in the meantime. But perhaps it's a systemd problem.
@netblue30 commented on GitHub (Mar 6, 2016):
Let's leave it open for now, I'll try to reproduce it here.
@curiosity-seeker commented on GitHub (Mar 9, 2016):
Now the situation has changed: Lately dnsmasq loads properly but my first dnscrypt-proxy instance doesn't. Hence I think that it's a systemd problem - perhaps /etc/systemd/system/dnscrypt-proxy.service.d/override.conf is not read properly/fast enough during the boot process. It seems that it's not Firejail-related. I'm going to try if delaying the start of that service solves the problem.