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

Compile error after updating to 0.2.4 #7

Closed
christophermichaelshaw opened this issue Dec 2, 2023 · 2 comments
Closed

Compile error after updating to 0.2.4 #7

christophermichaelshaw opened this issue Dec 2, 2023 · 2 comments

Comments

@christophermichaelshaw
Copy link

I received the below errors after updating to the recent 0.2.4 update. Works when I revert to 0.2.3.

Thanks for taking a look at this -- Let me know if I can provide any further logs or information to assist in troubleshooting!

[root@docker-node1 keepalived]# docker stack deploy keepalived --compose-file docker-compose.yml 
Updating service keepalived_keepalived (id: e8ca0ogd0uvcychqoc4iv86jz)
[root@docker-node1 keepalived]# docker service logs --follow keepalived_keepalived 
keepalived_keepalived.0.pgf26ltyzfux@docker-node1    | jq: error: Top-level program not given (try ".")
keepalived_keepalived.0.ucsk8nqq5x8u@docker-node1    | jq: error: Top-level program not given (try ".")
keepalived_keepalived.0.pgf26ltyzfux@docker-node1    | jq: 1 compile error
keepalived_keepalived.0.ucsk8nqq5x8u@docker-node1  | jq: 1 compile error
keepalived_keepalived.0.jrog4ek6ufz8@docker-node1    | jq: error: Top-level program not given (try ".")

Here's my config file:

version: '3.8'

services:
  keepalived:
    image: lolhens/keepalived-swarm:latest
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
      - /usr/bin/docker:/usr/bin/docker:ro
    networks:
      - host
    deploy:
      mode: global
      placement:
        constraints: [node.role == manager]
    environment:
      KEEPALIVED_VIRTUAL_IPS: "[IP_ADDRESS]"

networks:
  host:
    external: true
    name: host
@lhns
Copy link
Owner

lhns commented Dec 2, 2023

Thank you for the report! The error is fixed in v0.2.5.

@lhns lhns closed this as completed Dec 2, 2023
@christophermichaelshaw
Copy link
Author

Confirmed this is resolved. Thank you so much for your quick response and fix!

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

2 participants