Hello,
Thank you for this docker container.
I tried to connect to it using JDBC driver ( namely using the designer from dbschema.com ) but some reason the login does not work. Do you know how may I debug the connectivity issues ?
If I do locker logs no records are shown.

I believe that this image is not working :(

 starting container process caused "exec: \"dbsrv16\": executable file not found in $PATH".

Hi!
After start the docker with
docker run -d --name sqlAnywhere -p 2638:2638 jaschweder/sybase

I see the docker logs with and they are ok.

~ ❯ docker container logs sqlAnywhere
SQL Anywhere Network Server Version 16.0.0.2043
Developer edition, not licensed for deployment.

Copyright (c) 2014 SAP AG or an SAP affiliate company.
All rights reserved.
Use of this software is governed by the Sybase License Agreement.
Refer to http://www.sybase.com/softwarelicenses.

Connection limit (licensed seats): 3
Processors detected: 1 (containing 2 logical processors)
Maximum number of processors the server will use: 1 physical processor(s), 2 core(s)
This server is licensed to:
    Developer Edition
    Restricted Use
Running Linux 4.9.184-linuxkit #1 SMP Tue Jul 2 22:58:16 UTC 2019 on X86_64
Server built for X86_64 processor architecture
9116K of memory used for caching
Minimum cache size: 9116K, maximum cache size: 1838628K
Using a maximum page size of 4096 bytes
Multiprogramming level: minimum:2, current:20, maximum:80
Automatic tuning of multiprogramming level is enabled
Starting database "demo" (/opt/sqlanywhere16/demo.db) at Tue Dec 10 2019 19:11
Transaction log: demo.log
Starting checkpoint of "demo" (demo.db) at Tue Dec 10 2019 19:11
Finished checkpoint of "demo" (demo.db) at Tue Dec 10 2019 19:11
Database "demo" (demo.db) started at Tue Dec 10 2019 19:11
Database server started at Tue Dec 10 2019 19:11
Trying to start SharedMemory link ...
    SharedMemory link started successfully
Trying to start TCPIP link ...
Starting on port 2638
    TCPIP link started successfully
Now accepting requests

But i cant connect to the database because i'cant determine the ServiceName value in the connection string
"jdbc:sqlanywhere:Uid=DBA;pwd=sql;servicename=SQLAnywhereDemo"

Also enter the container with "docker exec -it sqlAnywhere /bin/bash" and try to run command dbisql or dblocate and in all cases it gives me Permission denied

Any help?
What is the ServiceName configured?
Why i can't execute commands inside the container?

Regards!!!

Hello,

Friend would love to use this image of yours for some tests here in docker but I can't make it work...

I made the Fork of your repository and gave the build but when it enters the environment and I try to go up a bank it gives that the command is very short.

I tried to do as you described in an issue, making a new Docker file and it didn't work either, it starts the database with the right name, but when I enter it shows the tables and everything else, only in the select it gives the information that the DBSPACE was not located to the table....

Can you make available via environment variable the possibility of passing the bank into the image? If you can't help me how to build from your repository without giving an error in sybase?

I'm studying docker, and I have this real scenario that I want to use, if you can help me understand and maybe build on top of your git as I'm studying I can even make improvements to it for you while I'm learning...

Can you help the friend here?

I am using the following docker-compose script to start up the container:

version: "3.8"
    
services:
  db:
    image: jaschweder/sybase
    ports:
        - "2638:2638"
        - "49152:49152"
    volumes:
      - type: bind
        source: .
        target: /opt/database
        volume:
          nocopy: true
volumes:
  mydata:

I have a database file on my local machine that I am mapping to the target in the container, and all is working fine. The only issue I am experiencing is that the original image always starts up demo.db.

How am I able to stop this from happening without having to recreate your image?

of the 3 sets of creds, only 'dba' works. Could you please update your image so that guest and sa work as well. Or just remove the wrong ones from the page and from DockerHub documentation.

Also why are all the files in bin64/ missing the execute bit?