deaerator Posted June 23, 2017 Share Posted June 23, 2017 Still having the same Error Quote Link to comment
Djoss Posted June 23, 2017 Author Share Posted June 23, 2017 Can you look at permissions inside the container? Quote Link to comment
deaerator Posted June 23, 2017 Share Posted June 23, 2017 how do you check to see if /storage is correct for permissions Quote Link to comment
Djoss Posted June 23, 2017 Author Share Posted June 23, 2017 Connect to your unRAID server via ssh and run the following command to login into container. docker exec -ti MKVToolNix sh Then you can check permissions as usual: ls -l / ls -l /storage And also look the directory where you save the video. Quote Link to comment
deaerator Posted June 23, 2017 Share Posted June 23, 2017 Everything looks the same as before. Quote Link to comment
Djoss Posted June 23, 2017 Author Share Posted June 23, 2017 From the container, are you able to create a file? touch /storage/MKVToolNix-Output (assuming this is where you save your videos from the application) Quote Link to comment
Djoss Posted June 23, 2017 Author Share Posted June 23, 2017 I meant: touch /storage/MKVToolNix-Output/testfile Quote Link to comment
deaerator Posted June 23, 2017 Share Posted June 23, 2017 "touch: /storage/MKVToolNix-Output/testfile: Read-only file system" Quote Link to comment
Djoss Posted June 23, 2017 Author Share Posted June 23, 2017 Looks like your /storage volume is read only... To confirm, you can see the content of the template by running this command on unRAID: cat /boot/config/plugins/dockerMan/templates-user/my-MKVToolNix.xml Did you installed the container via the Community Applications plugin? Quote Link to comment
deaerator Posted June 23, 2017 Share Posted June 23, 2017 My Bad completely. When you first uploaded your container I used that template via Community App page. And when It didn't work I just kept on using the template that was saved through unraid. I did a fresh install using the Community Applications and voila! It works now. Quote Link to comment
Djoss Posted June 23, 2017 Author Share Posted June 23, 2017 Great, happy to know that it's working Quote Link to comment
dlandon Posted June 30, 2017 Share Posted June 30, 2017 I am accessing the Docker by remote desktop and the keyboard repeat does not work when a key is held down. Is this an issue with this Docker, or all Dockers? Quote Link to comment
Djoss Posted June 30, 2017 Author Share Posted June 30, 2017 Currently, this is the expected behavior. The x11vnc server running inside the container automatically disables key autorepeat to work around common problems. This default behavior can be changed however. So let me know if you think it's something important to you. I could add the ability to pass extra parameters to x11vnc (via an environment variable). Quote Link to comment
dlandon Posted June 30, 2017 Share Posted June 30, 2017 19 minutes ago, Djoss said: Currently, this is the expected behavior. The x11vnc server running inside the container automatically disables key autorepeat to work around common problems. This default behavior can be changed however. So let me know if you think it's something important to you. I could add the ability to pass extra parameters to x11vnc (via an environment variable). It would be a nice feature, but I'm not sure it's worth it if it creates problems. Quote Link to comment
Djoss Posted July 5, 2017 Author Share Posted July 5, 2017 On 6/30/2017 at 7:27 AM, dlandon said: It would be a nice feature, but I'm not sure it's worth it if it creates problems. In the latest version, there is a new setting to pass custom options to x11vnc. Try to add the following one: -repeat This enables key autorepeat. You can test and see if it creates any problem for you (like duplicated characters during normal typing). Quote Link to comment
dlandon Posted July 5, 2017 Share Posted July 5, 2017 4 hours ago, Djoss said: In the latest version, there is a new setting to pass custom options to x11vnc. Try to add the following one: -repeat This enables key autorepeat. You can test and see if it creates any problem for you (like duplicated characters during normal typing). Seems to work just fine. Quote Link to comment
ikosa Posted July 6, 2017 Share Posted July 6, 2017 Container is running and i can log in from webui but i cant login from terminal? root@Tower:/# docker inspect --format="{{ .State.Running }}" MKVToolNix true root@Tower:/# docker exec -ti MKVToolNix /bin/bash rpc error: code = 2 desc = containerd: container not started Quote Link to comment
Djoss Posted July 6, 2017 Author Share Posted July 6, 2017 You need to use sh: docker exec -ti MKVToolNix sh Quote Link to comment
ikosa Posted July 6, 2017 Share Posted July 6, 2017 10 minutes ago, Djoss said: You need to use sh: docker exec -ti MKVToolNix sh this requires lots of editing on my scripts. Quote Link to comment
Djoss Posted July 6, 2017 Author Share Posted July 6, 2017 You could add a wrapper to your script that installs bash if needed: apk --no-cache add bash Quote Link to comment
ikosa Posted July 7, 2017 Share Posted July 7, 2017 23 hours ago, Djoss said: You could add a wrapper to your script that installs bash if needed: apk --no-cache add bash Thanks that really helped. But if you can add bash and curl to the container i will be appriciated. Or is there any proper and easy way to add bash and curl to my container that can survive container update? Quote Link to comment
Djoss Posted July 7, 2017 Author Share Posted July 7, 2017 I don't want to add packages that are not needed, because it increases uselessly the size of the image. And I guess that each user could have its own package preferences... However, if you check and install any missing packages yourself, you don't need to worry about container updates. And this add just a little overhead. You can have something like this: REQUIRED_PKG="bash curl" for PKG in $REQUIRED_PKG; do if ! apk info 2>/dev/null | grep -qw $PKG; then apk --no-cache add $PKG fi done Quote Link to comment
ljm42 Posted July 28, 2017 Share Posted July 28, 2017 On 7/6/2017 at 0:23 PM, Djoss said: You need to use sh: docker exec -ti MKVToolNix sh Thanks for posting this. I updated my docker-shell script: https://gist.github.com/ljm42/2b3bfd8ff886015bbce8 to work with your containers. First it tries: docker exec -it <name> bash and it that fails it tries: docker exec -it <name> sh Quote Link to comment
dockerstarter Posted September 19, 2017 Share Posted September 19, 2017 Very nicely done! I love the way you handle your docker container. One thing that i really miss is the abilty to change to my native language. Could you add language support for your containers ? I am not able to select the language for mkvtoolnix from the settings. The menu entry is empty. best regards dockerstarter Quote Link to comment
Djoss Posted September 20, 2017 Author Share Posted September 20, 2017 On 9/18/2017 at 10:39 PM, dockerstarter said: One thing that i really miss is the abilty to change to my native language. Could you add language support for your containers ? I'm looking into this. 1 Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.