[Bug]: OUTPUT_FILE on Docker not always working.

[GuruSR]

What happened?

I am running the Docker on an ASUSTOR RAID, if I don't specify OUTPUT_FILE, which I haven't, I get no file, no clue where it is going. /xmltv is aimed at one of two shares, I tried both, neither get it and the log has no compliants.

But, if I add the env for OUTPUT_FILE to /xmltv/xmltv.xml, it saves the file properly. So not sure what is going on. The log is useless, said everything worked properly.

Relevant log output

[kadeschs]

What happened?

I am running the Docker on an ASUSTOR RAID, if I don't specify OUTPUT_FILE, which I haven't, I get no file, no clue where it is going. /xmltv is aimed at one of two shares, I tried both, neither get it and the log has no compliants.

But, if I add the env for OUTPUT_FILE to /xmltv/xmltv.xml, it saves the file properly. So not sure what is going on. The log is useless, said everything worked properly.

Relevant log output

Came here to say the same thing. Since the last container update, xmltv.xml stopped being written to. My .zap2xmlrc config file includes outfile=/xmltv/xmltv.xml but no longer seems to work in latest version. Instead, I had to add the environmental variable OUTPUT_FILE to the container to get it to work again. I currently have OPT_ARGS set to -U -F -C /config/.zap2xmlrc but no longer seems to be reading the output_file.

[ferrellsl]

What happened?

I am running the Docker on an ASUSTOR RAID, if I don't specify OUTPUT_FILE, which I haven't, I get no file, no clue where it is going. /xmltv is aimed at one of two shares, I tried both, neither get it and the log has no compliants.
But, if I add the env for OUTPUT_FILE to /xmltv/xmltv.xml, it saves the file properly. So not sure what is going on. The log is useless, said everything worked properly.

Relevant log output

Came here to say the same thing. Since the last container update, xmltv.xml stopped being written to. My .zap2xmlrc config file includes outfile=/xmltv/xmltv.xml but no longer seems to work in latest version. Instead, I had to add the environmental variable OUTPUT_FILE to the container to get it to work again. I currently have OPT_ARGS set to -U -F -C /config/.zap2xmlrc but no longer seems to be reading the output_file.

On my system, xmltv.xml gets placed under /app/src if I don't specify an output path.

[ferrellsl]

Oh, I should add that it's placed under /app/src in the container.

[kadeschs]

Oh, I should add that it's placed under /app/src in the container.

I'm thinking that's what caused the silent break. If the previous container version had zap2xml living in /opt, and the latest version changed it to /app, that might explain why the bind-mounted /xmltv folder stopped receiving updates. zap2xml may successfully write to the XMLTV file inside the container producing no error. It's just not where it's expected. Hope to hear a confirmation from Jef on what may have changed with this version.

[jef]

OUTPUT_FILE and --outputFile= should work now. I think it was related to the args not working. Do you mind double checking?

[kadeschs]

I don't think removing the env variable OUTPUT_FILE worked for me with this update. After I removed the env and restarted container the xmltv.xml file did not get written to my binded folder path even though the logs says it was written without error.

`Fetching TV listings

Building XMLTV file

Writing XMLTV file

Last run time: Tue Jul 22 13:03:16 UTC 2025

Will run in 180 minutes`