Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

failed to parse config: * Invalid label: No argument or block type is named "logging". #154

Closed
jamjon3 opened this issue Feb 8, 2022 · 4 comments

Comments

@jamjon3
Copy link

jamjon3 commented Feb 8, 2022

The deployment fails when I add in 'logging' into the config under task. It works when I remove it. What am I doing wrong here???

failed to parse config:
Feb 08 22:44:49 somevmnmc01 nomad[67242]: | * Invalid label: No argument or block type is named "logging".

The task looks something like this:

  driver = "podman"
  config {
        image = "someimage"
        force_pull = true
        auth {
          username = "someuser"
          password = "somepassword"
        }
        logging = {
          driver = "journald"
          options = [
            {
              "tag" = "someapp"
            }
          ]
        }
  }
@towe75
Copy link
Collaborator

towe75 commented Feb 20, 2022

Are you building the driver from latest main branch? Seems like v0.3.0 binary did not yet have this feature.

@kamaradclimber
Copy link

This syntax is described in current documentation of the podman driver but seems to require an unreleased version of the driver.
Could you release the driver (or correct the documentation) please?

@jamjon3
Copy link
Author

jamjon3 commented May 13, 2022

@towe75 I'm building against the 0.3.0 (latest release). The last release was in 2021 and I'm seeing a lot of changes and I hope we are close to a new release and I agree with @kamaradclimber to just cut a new release

@lgfa29
Copy link
Contributor

lgfa29 commented Jul 15, 2022

Hi all,

I believe this is the same problem as #170 which should be fixed in v0.4.0. Would you mind trying with the new version?

I will also close this issue in favor of #170, so please post any updates there 🙂

Thank you.

@lgfa29 lgfa29 closed this as completed Jul 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants