mapping all available devices in docker-compose
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
I have a working docker-compose where I now need to bind not only one specific device but all available devices.
So instead of having something like:
devices
- '/dev/serial0:/dev/serial0'
I would like to do something like:
devices
- '/dev:/dev'
This gives me the following error:
container init caused "rootfs_linux.go:70: creating device nodes caused \"open /var/lib/docker/devicemapper/mnt/6a4...05af/rootfs/dev/pts/0: permission denied\""": unknown
I could I map all devices to my container?
docker docker-compose
add a comment |
I have a working docker-compose where I now need to bind not only one specific device but all available devices.
So instead of having something like:
devices
- '/dev/serial0:/dev/serial0'
I would like to do something like:
devices
- '/dev:/dev'
This gives me the following error:
container init caused "rootfs_linux.go:70: creating device nodes caused \"open /var/lib/docker/devicemapper/mnt/6a4...05af/rootfs/dev/pts/0: permission denied\""": unknown
I could I map all devices to my container?
docker docker-compose
Do you actually want to run this process in a Docker container? It sounds like you don't want the isolation that provides.
– David Maze
Nov 24 '18 at 11:41
add a comment |
I have a working docker-compose where I now need to bind not only one specific device but all available devices.
So instead of having something like:
devices
- '/dev/serial0:/dev/serial0'
I would like to do something like:
devices
- '/dev:/dev'
This gives me the following error:
container init caused "rootfs_linux.go:70: creating device nodes caused \"open /var/lib/docker/devicemapper/mnt/6a4...05af/rootfs/dev/pts/0: permission denied\""": unknown
I could I map all devices to my container?
docker docker-compose
I have a working docker-compose where I now need to bind not only one specific device but all available devices.
So instead of having something like:
devices
- '/dev/serial0:/dev/serial0'
I would like to do something like:
devices
- '/dev:/dev'
This gives me the following error:
container init caused "rootfs_linux.go:70: creating device nodes caused \"open /var/lib/docker/devicemapper/mnt/6a4...05af/rootfs/dev/pts/0: permission denied\""": unknown
I could I map all devices to my container?
docker docker-compose
docker docker-compose
asked Nov 24 '18 at 7:06
pnknrgpnknrg
792725
792725
Do you actually want to run this process in a Docker container? It sounds like you don't want the isolation that provides.
– David Maze
Nov 24 '18 at 11:41
add a comment |
Do you actually want to run this process in a Docker container? It sounds like you don't want the isolation that provides.
– David Maze
Nov 24 '18 at 11:41
Do you actually want to run this process in a Docker container? It sounds like you don't want the isolation that provides.
– David Maze
Nov 24 '18 at 11:41
Do you actually want to run this process in a Docker container? It sounds like you don't want the isolation that provides.
– David Maze
Nov 24 '18 at 11:41
add a comment |
1 Answer
1
active
oldest
votes
You can achieve this most easily by running a privileged container:
e.g compare:
docker run alpine ls -la /dev
vs
docker run --privileged alpine ls -la /dev
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53455982%2fmapping-all-available-devices-in-docker-compose%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
You can achieve this most easily by running a privileged container:
e.g compare:
docker run alpine ls -la /dev
vs
docker run --privileged alpine ls -la /dev
add a comment |
You can achieve this most easily by running a privileged container:
e.g compare:
docker run alpine ls -la /dev
vs
docker run --privileged alpine ls -la /dev
add a comment |
You can achieve this most easily by running a privileged container:
e.g compare:
docker run alpine ls -la /dev
vs
docker run --privileged alpine ls -la /dev
You can achieve this most easily by running a privileged container:
e.g compare:
docker run alpine ls -la /dev
vs
docker run --privileged alpine ls -la /dev
answered Nov 24 '18 at 8:54
Uku LoskitUku Loskit
31.1k87081
31.1k87081
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53455982%2fmapping-all-available-devices-in-docker-compose%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
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
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Do you actually want to run this process in a Docker container? It sounds like you don't want the isolation that provides.
– David Maze
Nov 24 '18 at 11:41