(Support Team)Docker not supporting arguments

[Dean_Johansson]

I’m trying to deploy a docker image using “docker run” as a command and “–cap-add SYS_ADMIN --device /dev/fuse” as flags/arguments. At the first deploy it worked but after I redeployed the app stopped working.

[Dean_Johansson]

According to the following topic, command arguments doesn’t work on koyeb. Is that right? If it is, why it did work the first time I tried?

Dockerfile Args is not working

I’m having two problems using Dockerfile args. First problem is ARGs in Dockerfile are not getting overridden. Second problem is the service instance fails to start. My Docker file has: ARG FOO=banana RUN echo $FOO > ./foo.txt In the Build and deployment settings, I override Args and set with: ["FOO=apple"] In the build logs, FOO is not overridden: #13 [7/8] RUN echo banana > ./foo.txt #13 DONE 0.1s Additionally, the service will fail to start. The Runtime logs don’t say what is failin…

[David]

Commands args works. The thread you shared is focusing on the mechanism to define environment variables that can be interpreted at build and run time.

What you are looking for is the capability to provide the docker args, and we do not support this. You could deploy your service in the privileged mode that you can select in the service configuration instead of --cap-add sys_admin even if it is not exactly the same. You won’t be able to specify --device /dev/fuse to the docker command.

[Dean_Johansson]

But it worked yesterday.

[Dean_Johansson]

Is there any way to allow the docker container to access the fuse?

[Dean_Johansson]

@David the first time I used the command args in koyeb, the flags --cap-add SYS_ADMIN --device /dev/fuse worked. Just when I redeployed it stopped working.