Create pulseaudio socket at system startup in Ubuntu 16.04












0















I'm running a docker container and I pass the pulse server environment variable to my container. The container is set to restart always policy. The container fails to run if the "pulseaudio.socket" is not present in the /tmp folder.



So to achieve my goal I added the command "pactl load-module module-native-protocol-unix socket=/tmp/pulseaudio.socket" to startup applications[the GUI program which is accessed by searcing startup programs]. This command creates a pulseaudio.socket file in the /tmp folder



This method works most of the time if the pulseaudio.socket file is created before docker starts the container. If docker starts the container before the pulseaudio.socket is created, the container fails to start.



To make sure the pulseaudio.socket is always created before docker starts the container I added the code "pactl load-module module-native-protocol-unix socket=/tmp/pulseaudio.socket" to /etc/rc.local and also tried to add it to init.d.



But adding the code to /etc/rc.local or init.d creates a pulse-PKdhtXMmr18n folder in the /tmp folder instead of the file pulseaudio.socket



How do I make sure that instead of pulse-PKdhtXMmr18n , file called pulseaudio.socket is always created ?



My main objective is to create /tmp/pulseaudio.socket file before docker starts or before docker tries to start a container with restart policy.



How do I do it?










share|improve this question







New contributor




node_man is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

























    0















    I'm running a docker container and I pass the pulse server environment variable to my container. The container is set to restart always policy. The container fails to run if the "pulseaudio.socket" is not present in the /tmp folder.



    So to achieve my goal I added the command "pactl load-module module-native-protocol-unix socket=/tmp/pulseaudio.socket" to startup applications[the GUI program which is accessed by searcing startup programs]. This command creates a pulseaudio.socket file in the /tmp folder



    This method works most of the time if the pulseaudio.socket file is created before docker starts the container. If docker starts the container before the pulseaudio.socket is created, the container fails to start.



    To make sure the pulseaudio.socket is always created before docker starts the container I added the code "pactl load-module module-native-protocol-unix socket=/tmp/pulseaudio.socket" to /etc/rc.local and also tried to add it to init.d.



    But adding the code to /etc/rc.local or init.d creates a pulse-PKdhtXMmr18n folder in the /tmp folder instead of the file pulseaudio.socket



    How do I make sure that instead of pulse-PKdhtXMmr18n , file called pulseaudio.socket is always created ?



    My main objective is to create /tmp/pulseaudio.socket file before docker starts or before docker tries to start a container with restart policy.



    How do I do it?










    share|improve this question







    New contributor




    node_man is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.























      0












      0








      0








      I'm running a docker container and I pass the pulse server environment variable to my container. The container is set to restart always policy. The container fails to run if the "pulseaudio.socket" is not present in the /tmp folder.



      So to achieve my goal I added the command "pactl load-module module-native-protocol-unix socket=/tmp/pulseaudio.socket" to startup applications[the GUI program which is accessed by searcing startup programs]. This command creates a pulseaudio.socket file in the /tmp folder



      This method works most of the time if the pulseaudio.socket file is created before docker starts the container. If docker starts the container before the pulseaudio.socket is created, the container fails to start.



      To make sure the pulseaudio.socket is always created before docker starts the container I added the code "pactl load-module module-native-protocol-unix socket=/tmp/pulseaudio.socket" to /etc/rc.local and also tried to add it to init.d.



      But adding the code to /etc/rc.local or init.d creates a pulse-PKdhtXMmr18n folder in the /tmp folder instead of the file pulseaudio.socket



      How do I make sure that instead of pulse-PKdhtXMmr18n , file called pulseaudio.socket is always created ?



      My main objective is to create /tmp/pulseaudio.socket file before docker starts or before docker tries to start a container with restart policy.



      How do I do it?










      share|improve this question







      New contributor




      node_man is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.












      I'm running a docker container and I pass the pulse server environment variable to my container. The container is set to restart always policy. The container fails to run if the "pulseaudio.socket" is not present in the /tmp folder.



      So to achieve my goal I added the command "pactl load-module module-native-protocol-unix socket=/tmp/pulseaudio.socket" to startup applications[the GUI program which is accessed by searcing startup programs]. This command creates a pulseaudio.socket file in the /tmp folder



      This method works most of the time if the pulseaudio.socket file is created before docker starts the container. If docker starts the container before the pulseaudio.socket is created, the container fails to start.



      To make sure the pulseaudio.socket is always created before docker starts the container I added the code "pactl load-module module-native-protocol-unix socket=/tmp/pulseaudio.socket" to /etc/rc.local and also tried to add it to init.d.



      But adding the code to /etc/rc.local or init.d creates a pulse-PKdhtXMmr18n folder in the /tmp folder instead of the file pulseaudio.socket



      How do I make sure that instead of pulse-PKdhtXMmr18n , file called pulseaudio.socket is always created ?



      My main objective is to create /tmp/pulseaudio.socket file before docker starts or before docker tries to start a container with restart policy.



      How do I do it?







      server sound pulseaudio docker






      share|improve this question







      New contributor




      node_man is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.











      share|improve this question







      New contributor




      node_man is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.









      share|improve this question




      share|improve this question






      New contributor




      node_man is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.









      asked yesterday









      node_mannode_man

      1012




      1012




      New contributor




      node_man is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.





      New contributor





      node_man is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.






      node_man is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.






















          1 Answer
          1






          active

          oldest

          votes


















          0














          I resolved the issue like this :



          My container has got a node script which starts the application and this application needs pulseaudio to run properly. So here is my docker run command.
          Notice the code in bold. Thats what I modified.



          Previous command



          sudo docker run --pid=host -dit --restart unless-stopped --env PULSE_SERVER=unix:/tmp/pulseaudio.socket --env PULSE_COOKIE=/home/$USER/pulseaudio.cookie --volume /tmp/pulseaudio.socket:/tmp/pulseaudio.socket --volume /home/$USER/pulseaudio.client.conf:/etc/pulse/client.conf --user $(id -u):$(id -g) --privileged --net=host ubuntu bash -c "node service.js && tail -F anything"



          Current command



          sudo docker run --pid=host -dit --restart unless-stopped --env PULSE_SERVER=unix:/tmp/pulseaudio.socket --env PULSE_COOKIE=/home/$USER/pulseaudio.cookie --volume /tmp:/tmp --volume /home/$USER/pulseaudio.client.conf:/etc/pulse/client.conf --user $(id -u):$(id -g) --privileged --net=host ubuntu bash -c "sh checksocket.sh && tail -F anything"



          In the previous command , the container used to start only if there was a pulseaudio.socket file in the /tmp folder of host.



          Now the current working command mounts --volume /tmp:/tmp instead of --volume /tmp/pulseaudio.socket:/tmp/pulseaudio.socket



          and sh checksocket.sh command executes the checksocket.sh file that I created inside the container.



          Here is the code of my checksocket.sh file :



          #!/bin/bash
          while sleep 0.5;
          do if [ -e /tmp/pulseaudio.socket ]
          then
          value="node service.js"
          exec $value
          break
          fi
          done


          This shell script keeps checking for the pulseaudio.socket file in the mounted /tmp folder and if it exists then only it starts my node service.



          In this way my container always starts whenever I reboot my machine and the node service starts once the shell script detect a pulseaudio.socket in the /tmp folder.



          I hope this helps someone who are trying to use pulseaudio with docker for the purpose of sound multiplexing or to avoid “device or resource busy” error(device or resource busy error comes when you use docker with alsa as alsa directly captures the sound card) on the host machine. Let me know if anybody needs more help






          share|improve this answer








          New contributor




          node_man is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
          Check out our Code of Conduct.




















            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "89"
            };
            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
            });


            }
            });






            node_man is a new contributor. Be nice, and check out our Code of Conduct.










            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1123375%2fcreate-pulseaudio-socket-at-system-startup-in-ubuntu-16-04%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









            0














            I resolved the issue like this :



            My container has got a node script which starts the application and this application needs pulseaudio to run properly. So here is my docker run command.
            Notice the code in bold. Thats what I modified.



            Previous command



            sudo docker run --pid=host -dit --restart unless-stopped --env PULSE_SERVER=unix:/tmp/pulseaudio.socket --env PULSE_COOKIE=/home/$USER/pulseaudio.cookie --volume /tmp/pulseaudio.socket:/tmp/pulseaudio.socket --volume /home/$USER/pulseaudio.client.conf:/etc/pulse/client.conf --user $(id -u):$(id -g) --privileged --net=host ubuntu bash -c "node service.js && tail -F anything"



            Current command



            sudo docker run --pid=host -dit --restart unless-stopped --env PULSE_SERVER=unix:/tmp/pulseaudio.socket --env PULSE_COOKIE=/home/$USER/pulseaudio.cookie --volume /tmp:/tmp --volume /home/$USER/pulseaudio.client.conf:/etc/pulse/client.conf --user $(id -u):$(id -g) --privileged --net=host ubuntu bash -c "sh checksocket.sh && tail -F anything"



            In the previous command , the container used to start only if there was a pulseaudio.socket file in the /tmp folder of host.



            Now the current working command mounts --volume /tmp:/tmp instead of --volume /tmp/pulseaudio.socket:/tmp/pulseaudio.socket



            and sh checksocket.sh command executes the checksocket.sh file that I created inside the container.



            Here is the code of my checksocket.sh file :



            #!/bin/bash
            while sleep 0.5;
            do if [ -e /tmp/pulseaudio.socket ]
            then
            value="node service.js"
            exec $value
            break
            fi
            done


            This shell script keeps checking for the pulseaudio.socket file in the mounted /tmp folder and if it exists then only it starts my node service.



            In this way my container always starts whenever I reboot my machine and the node service starts once the shell script detect a pulseaudio.socket in the /tmp folder.



            I hope this helps someone who are trying to use pulseaudio with docker for the purpose of sound multiplexing or to avoid “device or resource busy” error(device or resource busy error comes when you use docker with alsa as alsa directly captures the sound card) on the host machine. Let me know if anybody needs more help






            share|improve this answer








            New contributor




            node_man is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
            Check out our Code of Conduct.

























              0














              I resolved the issue like this :



              My container has got a node script which starts the application and this application needs pulseaudio to run properly. So here is my docker run command.
              Notice the code in bold. Thats what I modified.



              Previous command



              sudo docker run --pid=host -dit --restart unless-stopped --env PULSE_SERVER=unix:/tmp/pulseaudio.socket --env PULSE_COOKIE=/home/$USER/pulseaudio.cookie --volume /tmp/pulseaudio.socket:/tmp/pulseaudio.socket --volume /home/$USER/pulseaudio.client.conf:/etc/pulse/client.conf --user $(id -u):$(id -g) --privileged --net=host ubuntu bash -c "node service.js && tail -F anything"



              Current command



              sudo docker run --pid=host -dit --restart unless-stopped --env PULSE_SERVER=unix:/tmp/pulseaudio.socket --env PULSE_COOKIE=/home/$USER/pulseaudio.cookie --volume /tmp:/tmp --volume /home/$USER/pulseaudio.client.conf:/etc/pulse/client.conf --user $(id -u):$(id -g) --privileged --net=host ubuntu bash -c "sh checksocket.sh && tail -F anything"



              In the previous command , the container used to start only if there was a pulseaudio.socket file in the /tmp folder of host.



              Now the current working command mounts --volume /tmp:/tmp instead of --volume /tmp/pulseaudio.socket:/tmp/pulseaudio.socket



              and sh checksocket.sh command executes the checksocket.sh file that I created inside the container.



              Here is the code of my checksocket.sh file :



              #!/bin/bash
              while sleep 0.5;
              do if [ -e /tmp/pulseaudio.socket ]
              then
              value="node service.js"
              exec $value
              break
              fi
              done


              This shell script keeps checking for the pulseaudio.socket file in the mounted /tmp folder and if it exists then only it starts my node service.



              In this way my container always starts whenever I reboot my machine and the node service starts once the shell script detect a pulseaudio.socket in the /tmp folder.



              I hope this helps someone who are trying to use pulseaudio with docker for the purpose of sound multiplexing or to avoid “device or resource busy” error(device or resource busy error comes when you use docker with alsa as alsa directly captures the sound card) on the host machine. Let me know if anybody needs more help






              share|improve this answer








              New contributor




              node_man is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
              Check out our Code of Conduct.























                0












                0








                0







                I resolved the issue like this :



                My container has got a node script which starts the application and this application needs pulseaudio to run properly. So here is my docker run command.
                Notice the code in bold. Thats what I modified.



                Previous command



                sudo docker run --pid=host -dit --restart unless-stopped --env PULSE_SERVER=unix:/tmp/pulseaudio.socket --env PULSE_COOKIE=/home/$USER/pulseaudio.cookie --volume /tmp/pulseaudio.socket:/tmp/pulseaudio.socket --volume /home/$USER/pulseaudio.client.conf:/etc/pulse/client.conf --user $(id -u):$(id -g) --privileged --net=host ubuntu bash -c "node service.js && tail -F anything"



                Current command



                sudo docker run --pid=host -dit --restart unless-stopped --env PULSE_SERVER=unix:/tmp/pulseaudio.socket --env PULSE_COOKIE=/home/$USER/pulseaudio.cookie --volume /tmp:/tmp --volume /home/$USER/pulseaudio.client.conf:/etc/pulse/client.conf --user $(id -u):$(id -g) --privileged --net=host ubuntu bash -c "sh checksocket.sh && tail -F anything"



                In the previous command , the container used to start only if there was a pulseaudio.socket file in the /tmp folder of host.



                Now the current working command mounts --volume /tmp:/tmp instead of --volume /tmp/pulseaudio.socket:/tmp/pulseaudio.socket



                and sh checksocket.sh command executes the checksocket.sh file that I created inside the container.



                Here is the code of my checksocket.sh file :



                #!/bin/bash
                while sleep 0.5;
                do if [ -e /tmp/pulseaudio.socket ]
                then
                value="node service.js"
                exec $value
                break
                fi
                done


                This shell script keeps checking for the pulseaudio.socket file in the mounted /tmp folder and if it exists then only it starts my node service.



                In this way my container always starts whenever I reboot my machine and the node service starts once the shell script detect a pulseaudio.socket in the /tmp folder.



                I hope this helps someone who are trying to use pulseaudio with docker for the purpose of sound multiplexing or to avoid “device or resource busy” error(device or resource busy error comes when you use docker with alsa as alsa directly captures the sound card) on the host machine. Let me know if anybody needs more help






                share|improve this answer








                New contributor




                node_man is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.










                I resolved the issue like this :



                My container has got a node script which starts the application and this application needs pulseaudio to run properly. So here is my docker run command.
                Notice the code in bold. Thats what I modified.



                Previous command



                sudo docker run --pid=host -dit --restart unless-stopped --env PULSE_SERVER=unix:/tmp/pulseaudio.socket --env PULSE_COOKIE=/home/$USER/pulseaudio.cookie --volume /tmp/pulseaudio.socket:/tmp/pulseaudio.socket --volume /home/$USER/pulseaudio.client.conf:/etc/pulse/client.conf --user $(id -u):$(id -g) --privileged --net=host ubuntu bash -c "node service.js && tail -F anything"



                Current command



                sudo docker run --pid=host -dit --restart unless-stopped --env PULSE_SERVER=unix:/tmp/pulseaudio.socket --env PULSE_COOKIE=/home/$USER/pulseaudio.cookie --volume /tmp:/tmp --volume /home/$USER/pulseaudio.client.conf:/etc/pulse/client.conf --user $(id -u):$(id -g) --privileged --net=host ubuntu bash -c "sh checksocket.sh && tail -F anything"



                In the previous command , the container used to start only if there was a pulseaudio.socket file in the /tmp folder of host.



                Now the current working command mounts --volume /tmp:/tmp instead of --volume /tmp/pulseaudio.socket:/tmp/pulseaudio.socket



                and sh checksocket.sh command executes the checksocket.sh file that I created inside the container.



                Here is the code of my checksocket.sh file :



                #!/bin/bash
                while sleep 0.5;
                do if [ -e /tmp/pulseaudio.socket ]
                then
                value="node service.js"
                exec $value
                break
                fi
                done


                This shell script keeps checking for the pulseaudio.socket file in the mounted /tmp folder and if it exists then only it starts my node service.



                In this way my container always starts whenever I reboot my machine and the node service starts once the shell script detect a pulseaudio.socket in the /tmp folder.



                I hope this helps someone who are trying to use pulseaudio with docker for the purpose of sound multiplexing or to avoid “device or resource busy” error(device or resource busy error comes when you use docker with alsa as alsa directly captures the sound card) on the host machine. Let me know if anybody needs more help







                share|improve this answer








                New contributor




                node_man is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.









                share|improve this answer



                share|improve this answer






                New contributor




                node_man is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.









                answered 20 hours ago









                node_mannode_man

                1012




                1012




                New contributor




                node_man is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.





                New contributor





                node_man is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.






                node_man is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.






















                    node_man is a new contributor. Be nice, and check out our Code of Conduct.










                    draft saved

                    draft discarded


















                    node_man is a new contributor. Be nice, and check out our Code of Conduct.













                    node_man is a new contributor. Be nice, and check out our Code of Conduct.












                    node_man is a new contributor. Be nice, and check out our Code of Conduct.
















                    Thanks for contributing an answer to Ask Ubuntu!


                    • 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.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1123375%2fcreate-pulseaudio-socket-at-system-startup-in-ubuntu-16-04%23new-answer', 'question_page');
                    }
                    );

                    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







                    Popular posts from this blog

                    數位音樂下載

                    When can things happen in Etherscan, such as the picture below?

                    格利澤436b